ipconfig

ipconfig is the Windows network-configuration reporting tool — superficially the counterpart to the old *NIX ifconfig, but with DNS and DHCP management powers ifconfig never had. (On modern Linux the true successors are ip addr / resolvectl.)

The useful subset

ipconfig /all          # full config: MACs, DHCP, DNS servers, leases, suffixes
ipconfig /displaydns | more     # dump the resolver cache — a browsing-history goldmine
ipconfig /flushdns               # clear the resolver cache
ipconfig /registerdns            # re-register this host's A/PTR with its DNS server
ipconfig /release  & ipconfig /renew     # DHCP lease drop/re-acquire
ipconfig /showclassid <adapter>  /setclassid   # DHCP class IDs

Operational notes

• ipconfig /all is fast host fingerprinting: domain suffix (AD domain name), DNS servers (internal infrastructure map), DHCP scope — all before any scanning. See windows-reconnaissance-commands.
• /displaydns leaks recently resolved names — internal hosts, cloud endpoints, C2-adjacent infrastructure the box has talked to. Pure gold for target mapping with zero network noise (T1016/T1018-adjacent).
• /flushdns is the cover-your-tracks counterpart: clears that cache before anyone else reads it (anti-forensics, weak form — resolver logs and upstream DNS still know).
• PowerShell-native equivalents: Get-NetIPConfiguration, Get-DnsClientCache, Clear-DnsClientCache, Get-DnsClientServerAddress.

Related

• ping-command — neighboring reachability tool (and its cross-platform flag traps)
• windows-reconnaissance-commands — arp -a, netstat -ano and friends
• powershell-port-scanning — next step after mapping the local network config

Sources

• ipconfig - Microsoft Learn
• Get-DnsClientCache - Microsoft Learn