To find your DNS server IP address, use system network tools like ipconfig (Windows), ifconfig or scutil (macOS), or nmcli (Linux). These commands display the DNS server configured for your active network connection.
DNS servers translate domain names like google.com into IP addresses your device uses to connect to websites. Knowing your DNS server's IP helps troubleshoot connectivity issues, verify security settings, or switch to a faster public DNS like Cloudflare (1.1.1.1) or Google (8.8.8.8).
Each device on a network gets a DNS server setting automatically via DHCP or manually through static configuration. This setting is stored in your OS's network stack and accessible through command-line tools or GUI settings.
Your device receives DNS server information during network setup. Most home networks assign it dynamically via DHCP. When you connect to Wi-Fi or plug in an Ethernet cable, your router sends the DNS server IP as part of the network configuration.
If you're using a static IP setup, the DNS server IP must be entered manually. This is common in business environments or when setting up custom network configurations.
For example, a home network using a Netgear router typically assigns DNS servers like 192.168.1.1 (the router itself) or public DNS addresses such as 8.8.8.8 if set in the router's admin panel.
Use native OS tools to retrieve the DNS server IP. These methods work on desktops, laptops, and servers.
Open Command Prompt or PowerShell and run:
ipconfig /allLook for the "DNS Servers" entry under your active network adapter. For example:
DNS Servers . . . . . . . . . . . : 192.168.1.1
8.8.8.8This shows two DNS servers: the local router (192.168.1.1) and Google's public DNS (8.8.8.8).
You can also use PowerShell's Get-DnsClientServerAddress cmdlet:
Get-DnsClientServerAddress -AddressFamily IPv4Output includes interface index, address family, and server IPs. This method is preferred in scripts and automation.
Open Terminal and run:
scutil --get DNSOutput returns a list of DNS server IPs. Example:
{domain-name = ""; search-domain = { }; nameserver = (192.168.1.1, 1.1.1.1);}The "nameserver" field lists the actual DNS server IPs.
Alternatively, use:
networksetup -getdnsservers Wi-FiReplace "Wi-Fi" with your active interface name (e.g., "Ethernet"). This returns only the configured DNS servers.
Open a terminal and run:
nmcli dev show | grep 'IP4.DNS'Output shows DNS server IPs. Example:
IP4.DNS[1]: 192.168.1.1
IP4.DNS[2]: 8.8.8.8For systems without NetworkManager, use:
cat /etc/resolv.confLook for lines starting with "nameserver". Example:
nameserver 1.1.1.1
nameserver 1.0.0.1This file is updated dynamically by dhcpcd or systemd-resolved. Changes may be overwritten on reconnect.
Many users mistake their router's IP (like 192.168.1.1) for the DNS server IP. While routers often act as DNS servers, they are not always the same. A router may forward DNS requests to external servers.
Another error is assuming DNS servers are always public. In corporate or school networks, internal DNS servers (e.g., 10.0.0.10) handle internal domains and may not resolve internet sites.
A less obvious point: DNS server IPs can change. When switching between Wi-Fi networks, your DNS settings update automatically. On mobile devices, roaming between networks may trigger changing DNS changes.
Suppose a user reports slow loading times on websites. You suspect DNS resolution delays. Run:
nslookup google.comOutput shows the time taken to resolve the domain. If it takes over 2 seconds, the current DNS server may be slow.
Check the DNS server IP:
ipconfig /allResult shows DNS servers as 192.168.1.1 and 8.8.8.8. Test performance with:
ping 8.8.8.8If ping succeeds but nslookup is slow, the issue lies with DNS resolution, not network connectivity.
Switch to Cloudflare's DNS (1.1.1.1) by editing network settings. Re-run nslookup. If response time drops below 100ms, the original DNS server was the bottleneck.
| Platform | Command | Output Example | Notes |
|---|---|---|---|
| Windows | ipconfig /all |
DNS Servers . . . . . . . . . . . : 192.168.1.1, 8.8.8.8 |
Simple, widely available. Shows all adapters. |
| macOS | scutil --get DNS |
{nameserver = (1.1.1.1, 1.0.0.1);} |
Structured output. Best for scripting. |
| Linux | nmcli dev show |
IP4.DNS[1]: 192.168.1.1 |
Requires NetworkManager. Use /etc/resolv.conf if not installed. |
I once debugged a slow website issue on a client's MacBook. The default DNS was set to a regional provider with high latency. After running scutil --get DNS, I saw 10.10.10.1 as the primary server. Switching to 1.1.1.1 reduced DNS lookup time from 3.2 seconds to 0.15 seconds.
Always verify DNS server IPs when diagnosing network problems. A misconfigured or slow DNS server can cause timeouts, failed logins, or app crashes-even if the internet connection appears stable.