Viewing Settings With Ipconfig

ipconfig (Windows) and ifconfig or ip (Linux/macOS) display a device's current network settings: its IP address, subnet mask, default gateway, and more. When you need to know how a machine is configured right now, this is the tool. Confirming the local settings is one of the first checks in almost any connectivity problem.

The essentials ipconfig reports are the IP address, the subnet mask, the default gateway, and (with /all) the DNS servers. Together these four define how the device communicates. A missing or wrong value in any of them, like a blank gateway, immediately explains many "no internet" complaints.

Checking the IP address confirms the device has a valid, expected address for its network. If the address belongs to the wrong subnet, the device cannot reach local peers correctly. Verifying the IP is a fast way to spot misconfiguration or a DHCP problem before chasing more complex causes.

If you see an address starting with 169.254.x.x, that is APIPA (Automatic Private IP Addressing). It means the device asked for a DHCP address and got none, so it self-assigned a link-local address. APIPA is a clear sign of a DHCP failure: a dead DHCP server, a broken link to it, or exhausted addresses.

The default gateway is the router the device uses to reach other networks. If the gateway is missing or wrong, local traffic may work but the internet will not. ipconfig lets you confirm the gateway is set and correct, a frequent culprit when a device can reach LAN hosts but nothing beyond.

Running ipconfig /all reveals the configured DNS servers. If DNS is wrong or empty, names will not resolve even though raw connectivity works, the classic "ping by IP works, by name fails" pattern. Verifying DNS settings here pairs perfectly with ping and nslookup to confirm or rule out name-resolution issues.

ipconfig /all shows far more than the basics: the MAC address (physical address), whether DHCP is enabled, the DHCP server's address, lease times, and DNS suffixes. This full view is invaluable for deeper diagnosis, letting you confirm where the device got its settings and how long they last.

ipconfig /release tells the device to give up its current DHCP-assigned address. This is often the first half of a refresh when an address looks wrong or stale. After releasing, the device has no DHCP address until it requests a new one, so release and renew are usually used together.

ipconfig /renew asks the DHCP server for a fresh lease. Pairing release then renew forces the device to redo the DHCP process and pick up correct, current settings. This simple two-step fixes many addressing problems, especially after a DHCP server change or when a device is stuck with a bad lease.

ipconfig /flushdns clears the local DNS resolver cache. If a name recently changed its IP but your machine keeps using the old cached answer, flushing forces a fresh lookup. This resolves "the site moved but my PC still hits the old server" issues caused by stale cached DNS records.

On Linux and macOS, the modern command is ip address (older systems use ifconfig). DHCP renewal uses tools like dhclient, and DNS caches are cleared differently per system. The concepts match ipconfig exactly, only the commands differ. Knowing both the Windows and Unix tools makes you effective on any platform you meet.

Test your ipconfig knowledge.

You learned ipconfig. Key points:

• It shows IP, subnet mask, gateway, and (with /all) DNS.
• A 169.254.x.x address means APIPA and a DHCP failure.
• /release then /renew forces a fresh DHCP lease.
• /flushdns clears stale cached DNS answers.
• Linux/macOS use ip or ifconfig for the same job.