Public DNS Servers

Public DNS resolvers accept recursive queries from the internet (subject to each operator’s terms). Examples include Cloudflare 1.1.1.1, Google 8.8.8.8, Quad9 9.9.9.9, and OpenDNS. DNS Checkers uses a curated list of these IPs as comparison points when you investigate propagation. Choosing a public resolver for your laptop or router is a separate decision involving privacy, filtering features, and performance — always read the provider policy.

Why lists matter for diagnostics

After a DNS change, different resolvers expire caches on different clocks. Querying several well-known publics from one server will not reproduce every ISP on earth, but it quickly shows whether “the internet” still disagrees in obvious ways. DNS Checkers captions this clearly: public resolvers queried from this server, not a global VPS grid.

Privacy and filtering differences

Some resolvers emphasize privacy; others emphasize malware blocking or family filters. Blocking resolvers may return rewritten answers for certain names. If your check looks “wrong,” confirm whether the resolver filters the query type or domain category before assuming your authoritative zone is broken.

Custom resolvers

On the homepage you can add a custom public resolver IP for the current session. Private and metadata addresses are blocked to prevent SSRF. This is useful when you operate your own recursive service and want it compared alongside Cloudflare/Google during a migration.

Try the list in context via the homepage checker, keep learning on the blog, and review disclaimers before using results in change-control decisions.

Operational etiquette

Public resolvers are shared resources. DNS Checkers rate-limits tool usage and uses short timeouts so diagnostics stay polite. Do not script aggressive scraping against third-party resolvers from this platform or your own bots. If you need high-volume resolution for a product, run your own recursive infrastructure or purchase capacity under an explicit agreement.

When teaching juniors, use this list to demonstrate that “Google DNS” and “Cloudflare DNS” are products with policies, not magic. Have them compare answers after a deliberate TTL-friendly change and write down which resolver flipped first. That exercise builds intuition better than any fake world map of pins.

Keep this page bookmarked as a glossary while you explore Phase 2 email and IP tools. Knowing which resolver you are comparing against makes every propagation screenshot more meaningful for teammates and clients.

If a resolver on this list starts refusing queries from our host, DNS Checkers will show empty or error states rather than inventing city-level fantasy results — another deliberate trust choice.