Best DNS Servers: Choose for Privacy, Filtering, and Reliability

Best DNS Servers: Choose for Privacy, Filtering, and Reliability

Best DNS Servers: Choose for Privacy, Filtering, and Reliability

One household wants a resolver that blocks known malicious domains; another wants unfiltered answers and minimal retained logs. Their best choices of DNS servers may differ even on the same connection. Compare the policies and features first, then test each candidate from your own network.

A recursive DNS resolver finds the addresses associated with domain names on a device’s behalf. The best server for your DNS requests should answer reliably, fit your privacy preferences, and work with your devices. A quicker lookup may shorten the wait before a connection starts, but changing DNS does not generally increase the download rate of an established transfer.

Best DNS server choices for common needs

These leading public DNS servers are practical candidates. Addresses below are IPv4; each also publishes IPv6 addresses and encrypted endpoints. Features and policies described here were checked in November 2026.

Service Standard IPv4 addresses Useful distinction
Cloudflare 1.1.1.1 1.1.1.1, 1.0.0.1 Unfiltered resolution with a privacy-focused logging policy; separate Families options filter threats or threats plus adult content.
Google Public DNS 8.8.8.8, 8.8.4.4 General-purpose resolution, normally without content filtering, and published details about temporary and permanent logs.
Quad9 Secure 9.9.9.9, 149.112.112.112 Blocks domains associated with known threats; an unfiltered variant is available separately.

These are among the best DNS servers to compare, but their response times and availability vary by network route and location. Cloudflare says its public resolver deletes limited transaction and debug logs within 25 hours; its policy also describes limited packet sampling for troubleshooting. Read the full policy when selecting the best DNS resolver for your privacy needs.

Google’s policy says temporary logs containing client IP addresses and queries are normally deleted within 24–48 hours, with longer retention possible for security or abuse. It also retains sampled records with IP addresses replaced by less precise location information. For the best unfiltered DNS server, consider Google’s exceptions for security threats or legal requirements.

Quad9’s secure service blocks known malicious domains and offers a separate unfiltered address pair. Quad9 says it does not store end-user IP addresses. Threat filtering can prevent access to some dangerous destinations, but it cannot catch every threat and may occasionally block a legitimate domain.

Encryption and device support

All three providers support DNS over HTTPS (DoH) and DNS over TLS (DoT), which encrypt queries between a compatible client and the resolver. Encryption protects that leg of the trip; the resolver still processes the query. Entering an ordinary IP address alone does not ensure encrypted DNS is enabled.

To use a top DNS service across a home, configure the router if it supports your chosen protocol. The best encrypted DNS server also needs compatible client settings. Alternatively, configure individual computers or phones. Some browsers, VPNs, and apps use their own DNS settings, and IPv6 can use different resolver addresses. Check those paths if the chosen filter appears to be bypassed.

Keep both addresses from the same filtering service where possible. Mixing a filtered resolver with an unfiltered alternate can produce inconsistent protection, because devices do not always use the alternate only when the first fails. Save your original settings before changing them, especially on a work network where internal names may rely on a private resolver.

Test from your own connection

What is the best DNS server for your network? Measure actual DNS lookups, not just ping times. Test the candidates using the same device, connection, query type, and transport you intend to use. A command such as dig @1.1.1.1 example.com A reports a query time on systems with dig; replace the address for each service. It tests ordinary DNS, not DoH or DoT.

  1. Try repeated names. Query a small set of real domains several times per resolver and record response time, answer status, and failures. Repeated requests are likely to benefit from caches, which is representative of frequently visited sites.
  2. Try less familiar names. Test additional real names that have not appeared in your runs. This may exercise less-cached paths, though a public resolver can already have them cached from other users. A client cannot guarantee a provider-side cache miss just by clearing its own cache.
  3. Repeat at different times. Compare typical and slow responses, timeouts, and consistency when deciding which DNS server is best. Check that returned answers are sensible; filtering can intentionally change an answer.
  4. Test the actual setup. If you plan to use encrypted DNS through a browser or router, use a compatible DNS benchmark or client for that transport as well. Verify the provider with its own test page when available.

The best DNS servers for a household are the ones that resolve its everyday sites consistently as well as quickly. A resolver can return a different content-delivery location, so compare actual site behavior too; the fastest lookup does not always yield the fastest page.

Make the choice

Choose Cloudflare’s standard service when an unfiltered option and its stated privacy policy suit you. Choose Quad9 Secure when blocking known malicious domains matters more than an unfiltered answer. Choose Google Public DNS if its logging terms and general-purpose approach fit your needs. If your current provider resolves reliably and supports the features you want, keeping it is also a sound choice. Use local tests to choose the best DNS provider for your connection.