What Is a DNS Server and What Does It Know About You?
A DNS server is a specialised computer that translates human-readable domain names into the IP addresses that computers use to communicate. Every time you type a URL into your browser or click a link, your device sends a DNS query to its configured DNS server asking for the IP address associated with that domain. This query happens before any other network activity — it is the first step in every single web request you make.
Because DNS queries are the first step in every web request, your DNS server sees every domain you attempt to visit — not the full URL or the content of the page, but the domain name itself. This is sufficient information to build a detailed picture of your browsing habits: which news sites you read, which social media platforms you use, which health or financial services you consult, and when you are online. For your ISP, this data is commercially and legally valuable.
ISP-provided DNS servers are the default for most internet connections worldwide. When you connect to your home broadband or mobile data, your device automatically receives DNS server addresses from your ISP via DHCP. These are typically the ISP's own DNS resolvers, which log every query made through them. In many countries, ISPs are legally required to retain DNS logs for a specified period and to provide them to law enforcement on request.
Beyond logging, ISP DNS servers have several other limitations. They are often slower than modern public DNS alternatives because they run on older infrastructure with less investment in optimisation. They frequently implement DNS-based content blocking for government-mandated censorship or their own acceptable use policies. Some ISPs have been caught hijacking DNS error responses to redirect users to advertising pages rather than showing standard "domain not found" errors.
If you are using a VPN, your DNS queries should be routed through your VPN provider's private DNS servers rather than your ISP's. A properly configured VPN replaces your ISP DNS with its own servers, preventing your ISP from seeing your query data. However, DNS leaks can cause queries to bypass the VPN and reach your ISP even while the VPN is active and connected. If the tool above shows your ISP's DNS server while you are connected to a VPN, you have a DNS leak.
Changing your DNS server is one of the simplest and most impactful privacy improvements available to any internet user. Switching from your ISP's DNS to Cloudflare's 1.1.1.1 — which takes under two minutes and requires no software installation — removes your ISP's ability to monitor your DNS queries, typically improves website loading times, and is completely free. The guide below explains exactly how to make this change on any device or operating system.
ISP DNS vs Private DNS — What's the Difference?
The most significant difference between ISP DNS and private DNS is logging policy. ISP DNS servers routinely log every DNS query made by their subscribers, creating a comprehensive record of browsing activity that is stored for months or years. Private DNS providers like Cloudflare (1.1.1.1) and Quad9 (9.9.9.9) operate under strict no-logging policies — Cloudflare's policy is independently audited annually by KPMG, and Quad9 is operated by a non-profit foundation with a public commitment to query privacy. Google's 8.8.8.8 logs some query data but on a shorter retention schedule than most ISPs and does not link it to specific user identities.
Speed is the second major differentiator. Modern public DNS providers like Cloudflare and Google operate global Anycast networks with data centres in hundreds of cities worldwide, routing every query to the nearest server for minimal latency. ISP DNS servers are typically located in a handful of regional data centres with older hardware and higher response times. Independent benchmarks consistently show Cloudflare and Google DNS responding 30–50% faster than the average ISP DNS server for most consumer connections.
Content blocking is an area where ISP DNS and private DNS diverge significantly. ISP DNS servers in many countries are used to implement government-mandated website blocks — when a domain is ordered blocked, ISPs modify their DNS to return an incorrect response for that domain, preventing users from resolving it. Private DNS providers do not implement ISP-level content blocks, though Quad9 does block known malware domains as a security feature. For users in countries with extensive DNS-based censorship, switching to a private DNS can restore access to blocked content.
Privacy implications extend beyond just logging. ISP DNS queries are sent in plain text (unencrypted) over port 53, meaning anyone monitoring network traffic between your device and the DNS server — including the ISP itself, network administrators, or attackers on public Wi-Fi — can read every DNS query. Private DNS providers offer DNS-over-HTTPS (DoH) and DNS-over-TLS (DoT) variants that encrypt queries in transit, making them invisible to network observers. Using Cloudflare's DoH endpoint (1.1.1.1 with DoH enabled) provides both a fast, no-logging DNS and encrypted query transport — the most private DNS configuration available without a VPN.
How to Change Your DNS Server to a Private Alternative
- Step 1 — Choose Your New DNS Server: For most users, Cloudflare (primary: 1.1.1.1, secondary: 1.0.0.1) is the best all-round choice — it is the fastest public DNS resolver with a strict no-logging policy. Google (8.8.8.8 / 8.8.4.4) is an excellent alternative with maximum reliability. Quad9 (9.9.9.9 / 149.112.112.112) adds automatic malware-domain blocking and is operated by a non-profit.
- Step 2 — Change DNS on Windows 10/11: Open Settings → Network & Internet → your active connection (Wi-Fi or Ethernet) → Hardware properties → Edit DNS server assignment. Change from "Automatic (DHCP)" to "Manual", enable IPv4, and enter your chosen primary and secondary DNS addresses. On Windows 11, you can also select "DNS over HTTPS" in the encryption dropdown for each address if using Cloudflare or Google DNS.
- Step 3 — Change DNS on macOS: Open System Preferences → Network, select your active connection (Wi-Fi or Ethernet), and click Advanced. Navigate to the DNS tab, click the + button to add your new DNS server IP addresses, and remove any existing ISP entries. Click OK and then Apply — changes take effect immediately for new connections.
- Step 4 — Change DNS on iPhone/iOS: Go to Settings → Wi-Fi, tap the blue information icon (ⓘ) next to your connected network, scroll down to DNS and tap "Configure DNS". Switch from "Automatic" to "Manual", delete the existing ISP entries, and add your chosen DNS addresses. Note that this setting is per-network — you will need to configure it for each Wi-Fi network you use, or use a DNS profile for system-wide configuration.
- Step 5 — Change DNS on Android: Go to Settings → Network & Internet → Advanced → Private DNS (on Android 9+). Select "Private DNS provider hostname" and enter the hostname for your chosen provider:
one.one.one.onefor Cloudflare ordns.googlefor Google. This setting applies to all networks (Wi-Fi and mobile data) and uses DNS-over-TLS for encrypted queries automatically. - Step 6 — Change DNS on Your Router (applies to all devices): Log into your router's admin panel (typically at 192.168.1.1 or 192.168.0.1 — check the sticker on your router for credentials). Find the DNS settings under WAN, Internet, or DHCP settings and replace the existing DNS entries with your chosen addresses. This change applies the private DNS to every device on your home network automatically, including smart TVs, game consoles, and IoT devices that cannot be configured individually.
- Step 7 — Enable DNS-over-HTTPS for Encrypted Queries: After changing your DNS server, enable DNS-over-HTTPS (DoH) in your browser for an additional layer of privacy. In Chrome, go to Settings → Privacy and Security → Security → "Use secure DNS" and select Cloudflare or Google. In Firefox, go to Settings → Privacy & Security → scroll to "DNS over HTTPS" and enable it with your chosen provider. DoH encrypts your DNS queries so they cannot be read by your ISP even if they monitor your network traffic.
- Step 8 — Return to this page to verify the change worked: After making your DNS changes, come back to this page and click the "Re-check" button above. The tool should now show your new DNS provider (Cloudflare, Google, Quad9, etc.) instead of your ISP. If your ISP still appears, try flushing your DNS cache: on Windows run
ipconfig /flushdns, on Mac runsudo dscacheutil -flushcachein Terminal, then check again.
If Your VPN DNS Is Showing — Check for Leaks
If the DNS tool above shows a VPN provider's DNS server — such as NordVPN, ExpressVPN, Surfshark, or ProtonVPN — that is a positive result. It means your VPN is correctly routing your DNS queries through its own private servers, preventing your ISP from logging your browsing activity at the DNS level. This is the expected behaviour of a properly configured VPN and indicates that your DNS is protected.
However, if the tool shows your ISP's DNS server while you believe your VPN is active and connected, you have a DNS leak. A DNS leak means your DNS queries are bypassing the VPN tunnel and being sent directly to your ISP's DNS servers in plain text, exposing every domain you visit despite the VPN encrypting your other traffic. DNS leaks are common on Windows due to its Smart Multi-Homed Name Resolution feature and can occur on any operating system after VPN updates or network changes.
To confirm whether you have a DNS leak and check for additional vulnerabilities, run the full DNS leak test on the homepage, which analyses your DNS routing in detail. For a comprehensive privacy check covering DNS, IP, and WebRTC leaks simultaneously, use the VPN leak test — it runs all three tests in one pass and gives you a complete picture of your VPN's protection status.
We may earn a commission if you purchase through our link
Yes, your DNS server typically changes when you switch between Wi-Fi and mobile data because each network assigns its own DNS server via DHCP. Your home Wi-Fi uses your router's configured DNS (which defaults to your ISP's DNS unless you changed it), while your mobile data connection uses your mobile carrier's DNS servers. If you have manually configured DNS at the device level (rather than at the router level), your custom DNS settings apply on both Wi-Fi and mobile data. Using a VPN overrides DNS on both connection types, routing all queries through the VPN's private DNS regardless of the underlying network.