What Is My DNS Server? Find Your Current DNS Resolver
Your device’s DNS setting and the resolver that actually answers your queries are often two different machines. Here is how to find both, on every platform.
Why this page doesn’t just show your DNS server
Browser JavaScript is sandboxed: it cannot read your operating system’s network adapter settings. Revealing the upstream resolver requires an authoritative nameserver that observes which resolver asks it about a unique hostname — something a simple web page cannot fake.
The reliable way is to ask your device directly, using the commands below.
-
laptop, phone
Your device
Browser and OS issue the lookup.
-
192.168.1.1
Configured device DNS
The address in your network settings — often your router.
-
ISP cluster or 1.1.1.1
Upstream recursive resolver
Does the real work and queries authoritative servers.
Check your DNS server on any device
Pick your platform. Every command has a one-click copy button.
Windows reports configured resolvers through PowerShell or cmd. Run either in Windows Terminal.
> Get-DnsClientServerAddress -AddressFamily IPv4 | Select-Object -ExpandProperty ServerAddresses
Lists IPv4 resolver addresses for every active adapter.
> ipconfig /all | findstr /R /C:"DNS Servers"
Filters full adapter output down to active DNS servers.
Flush your DNS cache
After changing resolvers, clear cached answers so your device stops using stale records.
> ipconfig /flushdns
Clears the Windows DNS Client service cache.
$ sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Restarts mDNSResponder daemon on macOS.
$ resolvectl flush-caches
Flushes systemd-resolved local cache.
Transparent port 53 hijacking
Some ISPs and networks silently redirect all unencrypted DNS on UDP port 53 to their own resolvers — even when you’ve configured 8.8.8.8 or 1.1.1.1. Your settings look right, but a different resolver answers.
- Answers for non-existent domains redirect to an ISP search page.
- A leak test shows your ISP’s resolver despite custom settings.
- Encrypted DNS (DoH or DoT) works around it, because it can’t be redirected transparently.
Ready to compare resolvers?
See which public resolver answers fastest from your connection right now.
Run DNS Speed Test →