DNS is the “address book” your devices use to find websites. A faster, more reliable DNS resolver can reduce delays when pages start loading, and a privacy-focused resolver can reduce how much your ISP (or Wi-Fi hotspot) can observe about the domains you request. In this guide you’ll pick a good DNS option for the UK/EU/US, enable encrypted DNS (DoH/DoT), and verify it’s working—step by step.
Quick picks (UK/EU/US)
Best “set it and forget it” for most people
- Cloudflare 1.1.1.1 (speed + strong privacy defaults) — Great global performance and modern encrypted DNS options. Cloudflare documents that it deletes public resolver logs within about 25 hours and avoids storing client IPs in non-volatile storage (with limited sampled packets for troubleshooting). :contentReference[oaicite:0]{index=0}
- Quad9 (privacy + malware blocking) — A Swiss non-profit resolver designed around privacy and security; Quad9’s policy states it does not collect or record IP addresses. :contentReference[oaicite:1]{index=1}
Best for families / blocking obvious bad stuff
- Cloudflare “1.1.1.1 for Families” — easy malware (and optional adult-content) filtering options via dedicated IPs/hostnames. :contentReference[oaicite:2]{index=2}
- AdGuard DNS (ad/tracker blocking at DNS level) — can block ads/trackers for many apps, but may cause occasional site/app breakage; public server addresses are published by AdGuard. :contentReference[oaicite:3]{index=3}
Best for power users who want customization + optional data residency
- NextDNS — profiles, blocklists, and configurable logging/retention (including options like choosing where logs are stored). :contentReference[oaicite:4]{index=4}
Important: “Fastest DNS” depends on where you are (London vs Berlin vs New York) and your ISP routing. The best approach is: pick 1–2 reputable options, enable encrypted DNS, test speed/reliability for a day, then keep the winner.
What changing DNS actually improves (and what it doesn’t)
DNS affects how quickly your device can translate a domain (like example.com) into an IP address. On modern websites, your device may perform multiple lookups per page—so even small delays can add up. Google’s Public DNS documentation highlights that DNS lookups are frequent and can affect page loading behavior. :contentReference[oaicite:5]{index=5}
What DNS can improve
- Faster start of page loads (especially on “cold” cache, new tabs, or first visit).
- Reliability (fewer random “site not found” moments if your ISP resolver is flaky).
- Privacy on networks you don’t trust when using encrypted DNS (DoH/DoT), reducing eavesdropping on DNS traffic. :contentReference[oaicite:6]{index=6}
- Basic security filtering (malware/phishing blocklists) if you choose a filtering resolver like Quad9 or Cloudflare Families. :contentReference[oaicite:7]{index=7}
What DNS does NOT do
- It does not hide who you are when you log in. If you sign into Gmail/Instagram/banking, they still know it’s you.
- It does not encrypt the entire internet connection. It only covers DNS queries; HTTPS covers web traffic, and a VPN covers more.
- It won’t fix weak Wi-Fi. If your Wi-Fi signal is poor, fix that first.
How to choose DNS for speed & privacy
Use this simple checklist to choose a DNS provider that matches your goals.
1) Speed & uptime (the “anycast” effect)
Many public DNS services use globally distributed networks so you reach a nearby server automatically. This usually improves latency and reliability versus a slow ISP resolver, but the winner depends on your route.
2) Privacy policy (what gets logged)
- Cloudflare: commits to limiting and deleting resolver logs quickly (about 25 hours) and avoiding storage of client IPs in non-volatile storage, with limited exceptions for sampled packets. :contentReference[oaicite:8]{index=8}
- Quad9: states it does not collect or record IP addresses and treats IP addresses as personally identifiable information. :contentReference[oaicite:9]{index=9}
- Google Public DNS: explains it keeps temporary logs with IP addresses for 24–48 hours, and permanent logs are anonymized/aggregated for analysis. :contentReference[oaicite:10]{index=10}
- NextDNS: states that if not specifically requested by the user, no data is logged, and users control what’s logged and for how long (some features require retention). :contentReference[oaicite:11]{index=11}
3) Encrypted DNS support (DoH / DoT)
Encrypted DNS reduces on-path snooping and tampering between your device and the DNS resolver. DNS over HTTPS is standardized in RFC 8484, and DNS over TLS is described in RFC 7858. :contentReference[oaicite:12]{index=12}
4) Filtering needs (optional)
Filtering DNS can block malware, trackers, or adult content, but it can also cause false positives. If you need “maximum compatibility” (work apps, banking, gaming), start with a non-aggressive resolver (Cloudflare standard or Google), then move to filtering only if you want it.
5) Region notes (UK/EU/US)
- UK/EU privacy focus: Quad9 (Swiss non-profit policy) or Cloudflare with encrypted DNS are strong defaults. :contentReference[oaicite:13]{index=13}
- US mainstream reliability: Cloudflare or Google are common; review Google’s privacy/log retention details if privacy is your top concern. :contentReference[oaicite:14]{index=14}
- Need configurable data residency: NextDNS highlights log storage location options (US, EU, UK, Switzerland). :contentReference[oaicite:15]{index=15}
DNS comparison table (beginner friendly)
This table is designed for everyday users choosing between reputable options. Always prefer encrypted DNS (DoH/DoT) when possible, especially on public Wi-Fi.
| Provider | Best for | Filtering | Encrypted DNS | Notes on logging (high level) | Common setup info |
|---|---|---|---|---|---|
| Cloudflare 1.1.1.1 | Speed + privacy defaults | Optional (Families) | DoH/DoT supported :contentReference[oaicite:16]{index=16} | Public resolver logs deleted within ~25 hours; limited data handling described in policy. :contentReference[oaicite:17]{index=17} | Families DoH URLs + IPs documented. :contentReference[oaicite:18]{index=18} |
| Quad9 | Privacy + malware blocking | Yes (malware/phishing, configurable) | DoH/DoT endpoints published :contentReference[oaicite:19]{index=19} | Policy states it does not collect/record IP addresses. :contentReference[oaicite:20]{index=20} | Addresses: 9.9.9.9 and DoH/DoT hostnames. :contentReference[oaicite:21]{index=21} |
| Google Public DNS | Reliability + performance | No (generally non-filtering) | DoH/DoT available :contentReference[oaicite:22]{index=22} | Temporary logs with IP for 24–48 hours; permanent logs are anonymized/aggregated. :contentReference[oaicite:23]{index=23} | IPv4: 8.8.8.8 / 8.8.4.4 documented. :contentReference[oaicite:24]{index=24} |
| NextDNS | Customization + profiles | Yes (highly configurable) | DoH/DoT supported :contentReference[oaicite:25]{index=25} | States no logging unless requested; users control retention; some features require data retention. :contentReference[oaicite:26]{index=26} | Apple profile generator exists for native encrypted DNS. :contentReference[oaicite:27]{index=27} |
| AdGuard DNS | Ad/tracker blocking | Yes (default + family options) | Public setup + addresses published :contentReference[oaicite:28]{index=28} | Depends on mode; expect more blocking + higher chance of false positives than non-filtering DNS. | Addresses (default/family) documented (e.g., 94.140.14.14). :contentReference[oaicite:29]{index=29} |
Beginner setup (devices + router)
You can set DNS in two places: (A) the router (covers every device on your Wi-Fi) or (B) each device (more control). For most homes, router-level DNS is simplest.
Step-by-step plan (recommended)
- Pick one provider from the quick picks (start with Cloudflare 1.1.1.1 or Quad9).
- Set it on your router if you can (best coverage). If not, set it on your main devices.
- Enable encrypted DNS (DoH/DoT) if your device/router supports it. :contentReference[oaicite:30]{index=30}
- Verify using the tests below and browse normally for a day.
- If something breaks (rare apps, parental controls, work VPN), switch to a less aggressive DNS or disable filtering.
Option A: Set DNS on your router (covers the whole home)
- Log into your router admin panel (often 192.168.0.1 or 192.168.1.1).
- Find Internet / WAN / DNS settings.
- Set Primary DNS and Secondary DNS to your provider’s IP addresses.
- Save and reboot the router.
- Reconnect devices, then verify (see verification).
Tip: Add both IPv4 and IPv6 DNS if your router supports it, otherwise some devices may bypass your choice via IPv6.
Option B: Set DNS on individual devices (more control)
This is great for laptops/phones you travel with, or when you can’t change router settings (shared housing, workplace, hotel).
Turn on encrypted DNS (DoH/DoT) the simple way
Encrypted DNS helps protect your DNS requests from being read or modified on the network. DNS over HTTPS (RFC 8484) uses HTTPS (port 443), while DNS over TLS (RFC 7858) uses TLS (usually port 853). :contentReference[oaicite:31]{index=31}
Windows 11 (DoH)
- Go to Settings → Network & Internet.
- Select Wi-Fi (or Ethernet) → your connection.
- Find DNS server assignment → click Edit.
- Set it to Manual, enable IPv4, enter DNS servers.
- If Windows offers Encrypted only (DNS over HTTPS), enable it and select the template if available.
- Save.
Note: The exact DoH template availability depends on Windows builds and provider templates. If template isn’t available, use the provider’s app/profile or router DoH if supported.
Android (Private DNS / DoT)
- Open Settings → search for Private DNS.
- Choose Private DNS provider hostname.
- Enter the hostname provided by your DNS service (example: Quad9 publishes TLS hostnames like dns.quad9.net). :contentReference[oaicite:32]{index=32}
- Save, then browse and verify.
iPhone / iPad / macOS (profiles)
Apple devices often use configuration profiles for system-wide encrypted DNS. NextDNS provides an Apple profile generator to set this up natively. :contentReference[oaicite:33]{index=33}
Cloudflare Families (easy encrypted DNS URLs)
If you want malware filtering (and optional adult-content filtering), Cloudflare documents specific DoH URLs and IPs for Families. :contentReference[oaicite:34]{index=34}
Which should you use: DoH or DoT?
- DoH blends into normal HTTPS traffic and is widely supported by browsers and some OSes. :contentReference[oaicite:35]{index=35}
- DoT is clean and efficient on OS-level “Private DNS” (especially Android). :contentReference[oaicite:36]{index=36}
How to verify your DNS is working
1) Basic test: does browsing feel normal?
Open a few sites you use daily (news, email, streaming, banking). If everything works, move on.
2) Check DNS server settings (device level)
- Windows: Run
ipconfig /alland check “DNS Servers”. - macOS: System Settings → Network → your connection → DNS.
- Android: Settings → Private DNS should show “Connected”.
3) Make sure browsers aren’t overriding your DNS
Some browsers can use their own “Secure DNS” setting (DoH), which may override system DNS. If you want consistency, either disable browser DoH or set it to the same provider you chose. (This avoids “why does my test show a different DNS than my router?” headaches.)
Speed tuning tips (without breaking privacy)
- Stick to one resolver for a full day. DNS caching means instant switching can mislead you—give it time to stabilize.
- Avoid “ECS enabled” modes unless you know why you need them. Quad9 publishes a mode that enables EDNS Client Subnet (ECS). ECS can improve CDN location accuracy sometimes, but it can also reduce privacy. Quad9 clearly distinguishes service modes (recommended vs ECS-enabled). :contentReference[oaicite:37]{index=37}
- Use filtering only if you benefit. If you mainly want speed and fewer DNS leaks on public Wi-Fi, choose a non-aggressive resolver (Cloudflare standard or Google).
- On busy home networks, prefer router-level DNS. It reduces per-device misconfiguration and keeps everything consistent.
- Don’t confuse DNS speed with internet speed. DNS affects the “start,” but large downloads/streams depend on your ISP and Wi-Fi quality.
Troubleshooting (common problems)
Problem 1: “Some sites won’t load” after switching DNS
- Temporarily switch to a non-filtering resolver (Cloudflare standard or Google) to test.
- If that fixes it, your filtering DNS is blocking something needed—use a less aggressive profile.
- If it still fails, flush DNS cache and reboot router/device.
Problem 2: You set DNS on the router but your phone still uses something else
- Check if the phone is using Private DNS (Android) or a profile (iOS/macOS).
- Check if the browser has Secure DNS enabled with a different provider.
- Check IPv6: some devices may use IPv6 DNS if it’s available and router IPv6 DNS isn’t set.
Problem 3: Captive portals (hotel/airport Wi-Fi) break
Some captive portals don’t behave well with strict encrypted DNS. If you can’t sign in, temporarily disable Private DNS/DoH, complete the portal login, then re-enable it.
Problem 4: Work VPN + encrypted DNS conflicts
Corporate VPNs sometimes push their own DNS for internal domains. If internal tools fail, set DNS back to “Automatic” while connected to the work VPN (or configure split DNS if you know how).
Recommended DNS addresses & links (minimal, official sources)
Use these official pages for the latest addresses and policy details:
- Cloudflare 1.1.1.1 setup + Families (IPs and DoH URLs): Cloudflare 1.1.1.1 Setup :contentReference[oaicite:38]{index=38}
- Quad9 service addresses + DoH/DoT endpoints: Quad9 Addresses & Features :contentReference[oaicite:39]{index=39}
- Google Public DNS privacy statement (log retention details): Google Public DNS – Your Privacy :contentReference[oaicite:40]{index=40}
- Standards: DNS over HTTPS (RFC 8484) and DNS over TLS (RFC 7858): RFC 8484 and RFC 7858 :contentReference[oaicite:41]{index=41}
FAQ
Is changing DNS safe?
Yes—using reputable public resolvers is a common practice. The main “risk” is picking an overly aggressive filtering DNS that breaks some sites. Start with standard Cloudflare/Quad9/Google and only add filtering if you want it.
Will DNS make my internet faster for downloads and streaming?
DNS mostly improves how quickly sites start loading and how reliably domains resolve. Your actual download speed depends on your ISP, Wi-Fi strength, congestion, and the service you’re using.
DoH vs DoT: which is better for privacy?
Both encrypt DNS between you and the resolver. DoH is standardized in RFC 8484 and runs over HTTPS; DoT is standardized in RFC 7858 and runs over TLS. :contentReference[oaicite:42]{index=42} Choose whichever your device supports most cleanly (Android often prefers DoT via Private DNS; many desktops/browsers support DoH well).
Should I use Google DNS if I care about privacy?
Google Public DNS publishes clear retention details: temporary logs with IP addresses are deleted within 24–48 hours, while permanent logs are anonymized and used for analysis. :contentReference[oaicite:43]{index=43} If you prefer a resolver designed specifically around minimizing user data, consider Cloudflare’s public resolver commitments or Quad9’s policy statements. :contentReference[oaicite:44]{index=44}
What’s the best DNS choice for the UK and EU?
Cloudflare and Quad9 are strong defaults for many users. If you need configurable data residency (including UK/EU options) with customizable profiles, NextDNS highlights log storage location options and user-controlled retention. :contentReference[oaicite:45]{index=45}
Can DNS block ads?
Yes—DNS-level ad/tracker blocking can reduce ads in many apps and devices, but it’s not perfect (some ads come from the same domains as content). AdGuard DNS publishes public DNS options designed for this, but expect occasional breakage and test carefully. :contentReference[oaicite:46]{index=46}
%20Beginner-Friendly%20Setup.png)


