Cloudflare’s IPv6 resolver is the best default choice for most people who want fast, private DNS without content filtering. Use 2606:4700:4700::1111 and 2606:4700:4700::1001 if you want the IPv6 version of 1.1.1.1. Google DNS is still excellent, especially for reliability, but Cloudflare usually wins if your priority is privacy-first public DNS with low latency.
TLDR: Cloudflare 1.1.1.1 over IPv6 is fast, simple, and privacy-focused, while Google Public DNS is highly reliable and widely trusted. For example, a home user switching from an ISP resolver to Cloudflare may see DNS lookups drop from around 35 ms to 12 ms, depending on location and routing. If you want malware blocking, use Quad9 instead. If you want parental controls or ad blocking, look at AdGuard DNS, NextDNS, or Control D.
What is 1.1.1.1 IPv6?
1.1.1.1 is Cloudflare’s public DNS resolver. The name comes from its famous IPv4 address, but it also has IPv6 addresses. For IPv6-only networks, dual-stack homes, modern routers, and mobile carriers, these are the Cloudflare DNS addresses you need:
- Primary IPv6: 2606:4700:4700::1111
- Secondary IPv6: 2606:4700:4700::1001
Cloudflare also offers malware-blocking and family-filtered versions:
- Malware blocking: 2606:4700:4700::1112 and 2606:4700:4700::1002
- Malware and adult content blocking: 2606:4700:4700::1113 and 2606:4700:4700::1003
The regular 1.1.1.1 service does not block sites. That is the point. It resolves domain names quickly and tries to keep logging minimal.
Cloudflare IPv6 DNS vs Google IPv6 DNS
Google Public DNS is probably Cloudflare’s biggest rival. Its IPv6 addresses are easy to remember:
- Primary IPv6: 2001:4860:4860::8888
- Secondary IPv6: 2001:4860:4860::8844
Both services support modern DNS features. Both are stable. Both have huge global networks. The difference is mostly about privacy policy, performance in your region, and how much you trust each company with DNS metadata.
| Resolver | Best for | IPv6 addresses | Filtering |
|---|---|---|---|
| Cloudflare | Speed and privacy | 2606:4700:4700::1111, 2606:4700:4700::1001 | No, unless using special filtered addresses |
| Reliability and compatibility | 2001:4860:4860::8888, 2001:4860:4860::8844 | No | |
| Quad9 | Security blocking | 2620:fe::fe, 2620:fe::9 | Blocks known malicious domains |
| AdGuard DNS | Ad blocking and family protection | 2a10:50c0::ad1:ff, 2a10:50c0::ad2:ff | Yes |
Speed: Cloudflare is often the quickest, but test it
Cloudflare built 1.1.1.1 with speed as a selling point. In many cities, its resolver responds in under 15 ms. Google is often close. Sometimes it is faster. DNS speed depends on your ISP, peering, Wi-Fi quality, router, and distance to the nearest resolver node.
The catch is that online DNS speed charts can lie to you by being too general. A resolver that is fastest in London may not be fastest in rural Oregon or northern Poland. Expect to waste a few minutes testing if you care about every millisecond.
Use tools such as DNSPerf, GRC DNS Benchmark, or namebench alternatives. You can also run simple command-line checks with dig or nslookup. Test the same domain several times, since the first lookup may be slower than cached results.
Privacy: this is where Cloudflare stands out
Cloudflare says it does not sell DNS query data or use it to target ads. It also says it deletes most resolver logs quickly. That makes 1.1.1.1 attractive for users who dislike sending every domain lookup to their ISP.
Google Public DNS also has a clear policy, but some users are less comfortable giving more internet metadata to Google. That concern is fair. DNS requests can reveal a lot. They show which services your devices contact, when apps wake up, and which sites someone in a home tends to visit.
Still, no public DNS resolver makes you invisible. Your ISP can still see the IP addresses you connect to unless you use a VPN or encrypted proxy. Websites still see your traffic. DNS privacy helps, but it is not a magic cloak.
Encrypted DNS: DoH and DoT support
Cloudflare, Google, Quad9, AdGuard, NextDNS, and Control D all support encrypted DNS in some form. The two common options are:
- DNS over HTTPS: Often called DoH. It sends DNS queries over HTTPS.
- DNS over TLS: Often called DoT. It sends DNS queries through a dedicated encrypted channel.
Encrypted DNS can stop local networks, coffee shop Wi-Fi, and some ISPs from reading your DNS queries. It also helps prevent basic DNS tampering. It drives me crazy that router menus still make this harder than it should be. Some routers expose plain DNS fields but hide DoH and DoT behind “advanced” screens, if they support them at all.
When Google DNS is the better choice
Google DNS is a strong pick if you want maximum compatibility. It has been around since 2009, and many enterprise networks, routers, and troubleshooting guides assume Google DNS will work. If Cloudflare is oddly slow on your ISP, Google is the first alternative to try.
Google also handles massive traffic volumes with ease. For users who only want DNS that “just works,” 2001:4860:4860::8888 is a safe choice.
When Quad9, AdGuard, NextDNS, or Control D make more sense
Cloudflare and Google are general-purpose resolvers. They are not always the right fit. If you want DNS to block threats or unwanted content, other providers may suit you better.
- Quad9: Best for security. It blocks domains linked to malware, phishing, and botnets. Use 2620:fe::fe and 2620:fe::9.
- AdGuard DNS: Good for blocking ads, trackers, and adult content. It is simple to set up on phones and routers.
- NextDNS: Great for custom rules, analytics, blocklists, and per-device profiles. The free tier has query limits.
- Control D: Strong for advanced filtering, location-based rules, and power users who want fine control.
- OpenDNS: Useful for families and small offices that want category filtering.
If you manage kids’ tablets, smart TVs, and random IoT gadgets, plain Cloudflare may feel too bare. In that case, filtered DNS saves time. It will not replace proper device controls, but it can cut junk traffic fast.
Best setup for home users
For most homes with IPv6 enabled, set DNS on the router first. That gives every device the same resolver. Use Cloudflare if you want speed and privacy:
- IPv6 primary: 2606:4700:4700::1111
- IPv6 secondary: 2606:4700:4700::1001
- IPv4 primary: 1.1.1.1
- IPv4 secondary: 1.0.0.1
If some devices ignore router DNS, set DNS manually on those devices. Phones, browsers, and operating systems may use private DNS, secure DNS, or VPN DNS settings that override the router. Annoying? Yes. Common? Also yes.
Which IPv6 DNS resolver should you choose?
Choose Cloudflare 1.1.1.1 IPv6 if you want a fast, privacy-focused resolver with clean defaults. Choose Google Public DNS if you want proven reliability and near-universal compatibility. Choose Quad9 if blocking malicious domains matters more than raw speed.
For ad blocking and parental controls, pick AdGuard DNS, NextDNS, or Control D. For a basic home connection, Cloudflare is the easiest recommendation. It is quick, free, and simple to remember once you save the IPv6 addresses: 2606:4700:4700::1111 and 2606:4700:4700::1001.