A public DNS resolver is a recursive resolver operated by a third party and available to anyone on the internet. Well-known examples include Google Public DNS (8.8.8.8), Cloudflare (1.1.1.1) and Quad9 (9.9.9.9), most of which run on anycast addresses.
Why it matters
People switch from the ISP resolver for speed, reliability, newer features such as DoH, DoT and DNSSEC validation, or to avoid ISP filtering and NXDOMAIN rewriting. The trade-off is trust and privacy: the operator sees your queries, and policies differ by provider. For troubleshooting, public resolvers are a handy neutral reference. If a site fails on your ISP resolver but works on 8.8.8.8, the cause is likely a stale cache or filtering at the ISP, not your DNS records.
Example
dig @1.1.1.1 example.com A
dig @8.8.8.8 example.com A
dig @9.9.9.9 example.com AComparing the three tells you whether a change has spread to large caches.
Common mistakes
- Setting a public resolver as your domain's nameserver. It is for clients, not for hosting a zone.
- Breaking internal names by bypassing the corporate resolver.
- Assuming all of them filter or log traffic in the same way.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.