"Check my DNS" can mean two different things. Some people own a domain and want to know whether their records are live; for that, our DNS propagation checker does the job. Others mean something closer to home: which DNS server is my own device using right now?

This guide is about the second question. It matters more often than you'd think. A slow-loading site, a "server not found" error, a freshly installed privacy resolver you want to confirm, or a VPN you suspect is leaking queries: all of them start with knowing which resolver your machine actually talks to.

First, a quick idea of how the setup works

Almost every home network is set up the same way. Your laptop doesn't talk to Google or Cloudflare or your ISP directly. It asks the router, usually at an address like 192.168.1.1, and the router forwards the question to whichever resolver it was configured with. So the DNS server your device reports is often just the router, and the real resolver sits one step behind it. We'll come back to how to see past that.

Windows 10 and 11

The fastest route is PowerShell. Open it from the Start menu and run:

Get-DnsClientServerAddress -AddressFamily IPv4

That lists the servers for every adapter. Look at the one marked Wi-Fi or Ethernet. The older command works too, and shows more besides:

ipconfig /all

Scroll to the adapter you're using and find the line called DNS Servers. If you prefer clicking, go to Settings, Network and Internet, pick your connection, and open its hardware properties.

macOS

In System Settings, open Network, select your connection, choose Details and then the DNS tab. From Terminal, this is quicker and shows everything the system is really using:

scutil --dns | grep nameserver

You can also run networksetup -getdnsservers Wi-Fi. If it answers "There aren't any DNS Servers set on Wi-Fi", nothing is set manually, and your Mac is simply using whatever the router hands out.

Linux

Most modern distributions use systemd-resolved, and this is the command to try first:

resolvectl status

You'll see a section per network interface with its current DNS server. If you look at /etc/resolv.conf and only find 127.0.0.53, don't be alarmed. That's the local stub listener, and the real upstream servers are the ones resolvectl prints. On systems using NetworkManager, nmcli dev show | grep DNS gives the same information.

Android

Android is the awkward one. Since version 9 there's a Private DNS option under Settings, Network and internet. If it's set to Automatic or to a hostname such as dns.google, your phone is using encrypted DNS and ignores whatever the Wi-Fi network offers. If it's Off, the phone follows the network. Android rarely shows the DHCP-assigned server on screen, so for a definitive answer use the router-side method below.

iPhone and iPad

Open Settings, Wi-Fi, and tap the small (i) next to your network. Scroll down to Configure DNS. If it says Automatic, the address comes from the router and isn't displayed. If it says Manual, you'll see the servers someone entered. On mobile data, iOS uses your carrier's resolver unless a configuration profile or VPN overrides it.

Looking at the router

The router's own settings page, typically at 192.168.0.1 or 192.168.1.1, shows what the router forwards to. It's usually under Internet, WAN or DHCP. A blank or automatic setting means your ISP's resolver; anything else is whatever someone chose.

Seeing who is really answering

Because of the router layer, the address you find locally can be misleading. There's a neat trick that asks the internet what it saw instead. Google runs a special name that replies with the IP address of whoever asked:

nslookup -type=TXT o-o.myaddr.l.google.com

Run from our server, the answer was our own server's address. Run from your home network, it returns the public address of your resolver, which you can paste into our IP address lookup to see who owns it. A second option is nslookup whoami.akamai.net, which works the same way.

Try it after switching resolvers, and with your VPN on and then off. If the VPN is on but the address belongs to your ISP, your DNS queries are leaving outside the tunnel. That's what people mean by a DNS leak.

Testing that the server works

To compare resolvers side by side, ask each one the same question directly:

nslookup example.com 8.8.8.8
nslookup example.com 1.1.1.1
nslookup example.com

The first line of each reply, labelled Server, tells you who answered. If the first two work and the third fails, the resolver your device normally uses is the problem, and changing it is a quick fix. Our comparison of the best free public DNS servers helps you pick a replacement, and the guide to fixing DNS errors goes through everything else worth trying.

Remember: after changing DNS settings, flush your DNS cache so the machine stops serving answers it learned from the old server.

Is the default resolver good enough?

Often, yes. An ISP resolver sits close to you and tends to be quick. The reasons to change it are more specific: it's unreliable, it hijacks failed lookups to show search pages, it blocks things you want, or you simply prefer a different privacy policy. If none of those apply, leaving it alone is a valid choice, and knowing what it is gives you a baseline to compare against.

Checking a domain instead

If what you really wanted was to see how a domain's records look around the world, head back to the main checker, enter the domain, and choose the record type. You'll see what resolvers in dozens of countries answer, with TTLs and response times.