{"id":169233,"date":"2026-06-19T08:39:39","date_gmt":"2026-06-19T05:39:39","guid":{"rendered":"https:\/\/computingforgeeks.com\/?p=169233"},"modified":"2026-06-19T08:39:39","modified_gmt":"2026-06-19T05:39:39","slug":"verify-ip-settings-windows-mac-linux","status":"publish","type":"post","link":"https:\/\/computingforgeeks.com\/verify-ip-settings-windows-mac-linux\/","title":{"rendered":"Verify IP Settings on Windows, macOS, and Linux"},"content":{"rendered":"

By the end of this you’ll know the exact command to confirm a machine’s IP address, subnet mask, default gateway, and DNS server on any of the three desktop operating systems, and how to read the output so a misconfiguration jumps out at you. The graphical network settings panels show the same information, but the command line is faster, scriptable, and the same everywhere you connect, which is why it is worth learning once.<\/p>\n\n

This guide shows how to verify IP settings on Windows, macOS, and Linux with the real command output for each, a side-by-side table so you never mix up which command belongs to which OS, and what to do when an address starting with 169.254 shows up.<\/p>\n\n

Captured the output below on Windows, macOS 26, and Ubuntu 24.04 in June 2026.<\/em><\/p>\n\n

The four settings every device needs<\/h2>\n\n

Before the commands, know what you are looking for. Every device on a network needs four values configured correctly, and each one fails in its own way when it is wrong:<\/p>\n\n\n

\n
Setting<\/th>What it does<\/th>What breaks if it is wrong<\/th><\/tr><\/thead>
IP address<\/td>The device’s unique address on the network<\/td>No communication, or an address clash<\/td><\/tr>\n
Subnet mask<\/td>Splits the address into network and host parts<\/td>The device thinks local hosts are remote (or vice versa)<\/td><\/tr>\n
Default gateway<\/td>The router that reaches other networks<\/td>Local traffic works, but nothing off the subnet (no internet)<\/td><\/tr>\n
DNS server<\/td>Resolves names like example.com to addresses<\/td>Numbers work, names do not (“the internet is down”)<\/td><\/tr>\n<\/tbody><\/table><\/figure>\n\n\n

Every command below is just a way to read these four values back off a running machine. The trick is knowing which command each OS uses, so we will take them one at a time.<\/p>\n\n

Check IP settings on Windows<\/h2>\n\n

Windows uses ipconfig<\/code>. On its own it prints the address, mask, and gateway, which is enough for a quick look. Add the \/all<\/code> switch and it prints everything: the MAC address, whether DHCP is on, the DNS servers, and the lease times.<\/p>\n\n\n

\"Windows<\/figure>\n\n\n

Read it top to bottom for the four values: IPv4 Address<\/code> is the address, Subnet Mask<\/code> is the mask, Default Gateway<\/code> is the router, and DNS Servers<\/code> is name resolution. The DHCP Enabled: Yes<\/code> line tells you the address came from a DHCP server rather than being set by hand, and the lease times tell you when it renews. If you ever need to drop and reacquire a lease, ipconfig \/release<\/code> followed by ipconfig \/renew<\/code> does it.<\/p>\n\n

Check IP settings on macOS<\/h2>\n\n

macOS keeps two tools side by side. The classic ifconfig<\/code> still works and shows the address and MAC, but the friendlier networksetup -getinfo<\/code> prints the address, mask, router, and a clean summary for a named service in one shot. For DNS, scutil --dns<\/code> lists the resolvers the system is actually using.<\/p>\n\n\n

\"macOS<\/figure>\n\n\n

The part that trips people up on macOS is the subnet mask in ifconfig<\/code>, which prints in hexadecimal (0xffffff00<\/code>) rather than dotted decimal. That hex value is just 255.255.255.0<\/code> written another way, and networksetup -getinfo<\/code> shows it in the familiar decimal form if you prefer. To get the service name to pass to networksetup<\/code>, run networksetup -listallnetworkservices<\/code> first.<\/p>\n\n

Check IP settings on Linux<\/h2>\n\n

Modern Linux uses the ip<\/code> command from iproute2. The old ifconfig<\/code> is deprecated and often not installed at all. Three commands cover the four values: ip addr<\/code> for the address and mask, ip route<\/code> for the gateway, and resolvectl status<\/code> for DNS.<\/p>\n\n\n

\"Linux<\/figure>\n\n\n

Two things look different from Windows and macOS here. The address and mask come together as a CIDR prefix, 192.168.1.51\/24<\/code>, where \/24<\/code> is the same thing as a 255.255.255.0<\/code> mask. And the gateway is not in the address output at all; it is the default via<\/code> line of ip route<\/code>. On any distro, cat \/etc\/resolv.conf<\/code> is a universal fallback for seeing the DNS servers if resolvectl<\/code> is not present.<\/p>\n\n

Every command, side by side<\/h2>\n\n

This is the table to memorise. Same task, different command per OS, so you never reach for ipconfig<\/code> on a Mac or ifconfig<\/code> on a modern Linux box:<\/p>\n\n\n

\n
Task<\/th>Windows<\/th>macOS<\/th>Linux<\/th><\/tr><\/thead>
Show IP + mask<\/td>ipconfig<\/code><\/td>ifconfig en0<\/code><\/td>ip addr<\/code><\/td><\/tr>\n
Show everything<\/td>ipconfig \/all<\/code><\/td>networksetup -getinfo \"Wi-Fi\"<\/code><\/td>ip addr; ip route; resolvectl status<\/code><\/td><\/tr>\n
Show gateway<\/td>ipconfig<\/code><\/td>netstat -rn<\/code> \/ route -n get default<\/code><\/td>ip route<\/code><\/td><\/tr>\n
Show DNS<\/td>ipconfig \/all<\/code><\/td>scutil --dns<\/code><\/td>resolvectl status<\/code><\/td><\/tr>\n
Show MAC address<\/td>ipconfig \/all<\/code><\/td>ifconfig en0<\/code><\/td>ip link<\/code><\/td><\/tr>\n
Renew DHCP lease<\/td>ipconfig \/renew<\/code><\/td>sudo ipconfig set en0 DHCP<\/code><\/td>sudo networkctl renew eth0<\/code><\/td><\/tr>\n
Flush DNS cache<\/td>ipconfig \/flushdns<\/code><\/td>sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder<\/code><\/td>sudo resolvectl flush-caches<\/code><\/td><\/tr>\n<\/tbody><\/table><\/figure>\n\n\n

One caveat on the Linux column: the renew command shown is for systems running systemd-networkd or netplan, which is the Ubuntu and Debian default. On a desktop managed by NetworkManager, use nmcli device reapply eth0<\/code> instead. The read commands (ip addr<\/code>, ip route<\/code>, resolvectl<\/code>) are identical either way.<\/p>\n\n

What an address starting 169.254 means<\/h2>\n\n

Here is the one diagnostic worth memorising. If a Windows machine shows an IPv4 address in the 169.254.x.x<\/code> range, it did not get an address from DHCP. This is APIPA (Automatic Private IP Addressing): when a client sends DHCP requests and gets no answer, it assigns itself a link-local address in 169.254.0.0\/16<\/code> so it can at least talk to other machines on the same wire. It cannot reach the gateway or the internet.<\/p>\n\n

If you see a 169.254 address, the fix is upstream, not on the client. Check that the DHCP server is actually running, that the switch port is in the right VLAN, and that the cable and network adapter are up. On the Cisco side, a port in the wrong VLAN is a common cause, which you would confirm with the interface status counters<\/a>. Once DHCP answers again, ipconfig \/renew<\/code> on Windows (or reconnecting the interface elsewhere) pulls a real address.<\/p>\n\n

Practice verifying IP settings<\/h2>\n\n

Flip the cards to lock in which command belongs to which OS, then take the quiz, which includes the APIPA diagnostic and the command-matching question. For background on what each of these four values actually means, the IPv4 addressing guide<\/a> covers them in depth, and the full path is the CCNA 200-301 study roadmap<\/a>.<\/p>\n\n

Loading flashcards...<\/div><\/div>\n\n
Loading quiz...<\/div><\/div>\n\n

The 30-second IP check<\/h2>\n\n

When you sit down at an unfamiliar machine and need its network settings fast, this is the one command per OS that shows all four values at once:<\/p>\n\n