ipconfig is a built-in Windows command that displays and manages your machine's TCP/IP network configuration. If you're troubleshooting a connection, diagnosing a DNS issue, or just need to know your IP address fast - this is your first stop.

Open Command Prompt (Win + R → type cmd → Enter) and you're ready.

Core Commands

Basic output - your IPs at a glance:

Command 
ipconfig

Returns your active network adapters with their IPv4 address, subnet mask, and default gateway. Clean, fast, essential.

Full detail - everything your adapter knows:

Command 
ipconfig /all

Adds MAC address, DHCP status, DNS servers, lease times, and IPv6 addresses. Use this when you need the full picture - especially when comparing config against a network policy or firewall rule.

Release your current IP:

Command 
ipconfig /release

Drops the DHCP-assigned IP address on all adapters. Useful when your IP has gone stale or you're switching networks.

Request a new IP from DHCP:

Command 
ipconfig /renew

Forces a fresh DHCP lease. Run /release first, then /renew to do a full reset. Fixes most "connected but no internet" issues caused by bad DHCP assignments.

Flush the DNS cache:

Command 
ipconfig /flushdns

Clears locally cached DNS records. Essential when a domain resolves to a stale or incorrect IP - common after DNS migrations, CDN switches, or misconfigured hosts files.

Display cached DNS entries:

Command 
ipconfig /displaydns

Shows every DNS record currently cached on your machine. Useful for confirming whether a DNS update has propagated locally yet.

Quick Troubleshooting Flow

Problem Command
What's my IP? ipconfig
Check DNS servers ipconfig /all
Site not loading after DNS change ipconfig /flushdns
No IP assigned ipconfig /release → ipconfig /renew
Confirm DNS propagation locally ipconfig /displaydns

The Linux / macOS Equivalent

ipconfig is Windows-only. On Linux and macOS, the equivalent commands are:

Command 
ip addr          # Modern Linux
ifconfig         # Legacy Linux / macOS

Bottom line: ipconfig /all and ipconfig /flushdns cover 90% of real-world network troubleshooting scenarios. Learn those two, and you'll solve most issues before they escalate.

Real Troubleshooting Workflow (In Order)

When a user says "internet is down," run commands in this order:

  1. ipconfig
  2. ipconfig /all
  3. ping <default-gateway>
  4. ping 8.8.8.8
  5. nslookup example.com
  6. ipconfig /flushdns then retry
  7. ipconfig /release and ipconfig /renew if DHCP looks wrong

Why this sequence works:

  • It separates local adapter problems from DNS problems.
  • It avoids wasting time resetting DNS when the gateway is unreachable.
  • It gives enough data for escalation if issue is upstream.

Common Mistakes

Flushing DNS for every issue

/flushdns helps stale name resolution, not cable faults, Wi-Fi instability, or ISP outages.

Releasing IP on a remote machine without backup access

If you run /release remotely on a machine with a fragile connection, you might cut off your own management access.

Ignoring adapter details in /all

The details often reveal:

  • wrong DNS resolvers
  • APIPA address (169.254.x.x) meaning DHCP failure
  • old lease state that points to a DHCP issue

Useful Command Pairings

ipconfig is strongest when combined with:

  • nslookup for DNS server behavior
  • tracert for routing visibility
  • netsh interface ip show config for interface config checks

Example:

Command 
ipconfig /all
nslookup iptoolspro.com
tracert iptoolspro.com

That set helps you distinguish resolver issues from path/latency issues.

Quick Indicators You Can Trust

  • 169.254.x.x -> DHCP failed
  • DNS server missing/unexpected -> likely resolver policy issue
  • Gateway unreachable but adapter has valid IP -> local network path issue
  • IP works but domain fails -> DNS issue

Bottom Line (Operational)

ipconfig is not just "show my IP." It is a fast diagnostic layer for DHCP, DNS, and interface state. Use a fixed command order, and you will resolve most Windows network incidents faster and with fewer random fixes.