What Is a Public DNS Server and Why Would I Use One?

Updated

A public DNS server is a DNS resolver that anyone can use, usually operated by a company, nonprofit, or community project rather than your internet provider. You use one by replacing the DNS addresses your ISP assigned with a public address such as 8.8.8.8 (Google Public DNS) or 1.1.1.1 (Cloudflare). People switch to public DNS mainly for three reasons: faster or more reliable lookups, different privacy and logging policies than their ISP, and content filtering or family-safety options. The tradeoffs are real, though — you are trusting a third party with your lookup traffic, and some public resolvers filter or redirect results.

Public DNS vs. your ISP's default DNS

When your device connects to a network, it is normally handed DNS server addresses automatically (via DHCP). Those usually belong to your ISP. A public DNS server does the same job — translating domain names into IP addresses — but it is reachable by anyone and is not tied to your connection.

Dimension ISP default DNS Public DNS
Who operates it Your internet provider A third-party operator (Google, Cloudflare, Quad9, etc.)
Setup Automatic Usually manual, or via router settings
Logging policy Varies, often not published Often published, and varies widely between providers
Filtering Sometimes (ISP-level blocks) Depends on the resolver — some filter, some don't
Redundancy Usually two servers Most providers publish primary + secondary, and often IPv6

The publicdns.xyz list notes that primary servers are sometimes called preferred and secondary servers alternate, and that primary and secondary addresses can be "mixed and matched" to add another layer of redundancy. That is a useful practical point: you are not locked into one provider's pair.

Why people switch to a public DNS server

  • Speed and reliability. If your ISP's resolver is slow, overloaded, or frequently down, a large public resolver can respond faster. This is the most common reason, but results vary by location and network — a public resolver is not automatically faster than a good local one.
  • Privacy and logging differences. Public resolvers publish different retention and logging practices. If you want to avoid your ISP seeing every domain you look up, a public resolver shifts that visibility to the resolver operator instead of removing it.
  • Filtering and safety. Some resolvers block malware, phishing, or adult content. Quad9, for example, is positioned around security filtering, and services like OpenDNS and SafeDNS offer filtering-oriented options. This is a feature for some users and an unwanted restriction for others.
  • Bypassing resolver-level blocks. If your ISP's DNS blocks or redirects certain domains, a public resolver may return the real answer. This does not bypass all forms of blocking, and it may conflict with your network's rules or terms of service.
  • Consistency across networks. Using the same resolver everywhere can give you predictable behavior when you move between Wi-Fi networks.

How to actually change your DNS

The exact menus differ by operating system and router, but the inputs and expected result are the same.

  1. Pick a primary and secondary address from a provider you trust — for example 1.1.1.1 and 1.0.0.1, or 8.8.8.8 and 8.8.4.4.
  2. Open your network settings (per-device) or your router's admin page (network-wide).
  3. Find the DNS configuration and switch it from automatic to manual.
  4. Enter the primary address in the first field and the secondary in the second. Add IPv6 addresses if your network uses IPv6.
  5. Save and reconnect.
  6. Verify: visit a DNS leak test page or run a lookup and confirm the resolver responding is the one you set, not your ISP's.

Setting it on the router covers every device on the network; setting it per-device only affects that device and is overridden if the router forces its own DNS.

Limitations and things to check first

  • You are still trusting someone. A public resolver sees your lookup traffic. Read the provider's privacy policy before assuming it is more private than your ISP.
  • Filtering may surprise you. A resolver that blocks malicious domains can also block legitimate ones. If a site stops resolving after you switch, test with a different resolver before assuming the site is down.
  • CDN and geo-location effects. Some content delivery networks place servers based on which resolver you use. A distant public resolver can occasionally route you to a farther server, which may hurt speed rather than help it.
  • Not a privacy cure-all. DNS is only one part of your traffic. Encrypted DNS (DoH/DoT) and a VPN address different parts of the problem.
  • Availability. Public resolvers can be blocked or throttled on some networks, including corporate and campus networks.

Choosing between providers

The publicdns.xyz list groups providers by region and purpose, which is a reasonable way to narrow the field:

  • General-purpose, large-scale: Google Public DNS, Cloudflare, OpenDNS, Quad9.
  • Security/filtering-oriented: Quad9, OpenDNS, Comodo Secure DNS, SafeDNS, Norton ConnectSafe.
  • Regional options: AliDNS, Baidu Public DNS, DNSPod Public DNS+, 114DNS, OneDNS, and others aimed at users in specific countries.
  • Community/uncensored: OpenNIC, UncensoredDNS.

There is no single best public DNS server. Pick based on what you actually need — speed, a published privacy policy, filtering, or regional latency — then test it on your own connection, since performance depends on your location and network more than on any ranking.