GrandSpeedVisit Website →
← Back to blog

15 Minute Test to Find the Fastest DNS for Gaming: Cloudflare or Quad9 First

October 7, 2026
15 Minute Test to Find the Fastest DNS for Gaming: Cloudflare or Quad9 First

Try Cloudflare DNS (1.1.1.1) or Quad9 (9.9.9.9) first, with Google Public DNS (8.8.8.8) as a backup. These three resolvers tend to post the lowest lookup times for most networks, but actual performance depends heavily on your location and ISP routing, so the only way to know for sure is to run a DNS latency test from your own connection before committing to one.

TL;DR:

  • Running local DNS latency tests is essential because online benchmarks often do not reflect your actual network performance.
  • Selecting a resolver depends on your priority: Cloudflare or Quad9 typically offer the fastest lookups, while NextDNS and OpenDNS provide more control over filtering.
  • DNS impact is limited to login, matchmaking, and patch downloads; it does not influence in-game ping or real-time performance during gameplay.
  • Using DNS tools like dig or dnsping and testing with cached and fresh domains help identify the lowest latency for your setup.
  • Changing DNS settings at the router level simplifies network management, especially if multiple devices are involved, but individual device setup can be better for specific cases.
Grandspeed
Test DNS Performance on Your Connection
Compare DNS resolution times alongside latency, jitter, packet loss, and other network conditions using GrandSpeed’s browser-based testing tools.
Run a network test

Table of Contents

The best DNS servers for gaming compared side by side

A fast DNS resolver shortens the time it takes your device to translate a game server's domain into an IP address. That lookup happens before matchmaking, patch downloads, and voice chat connections, so a slow or unreliable resolver adds friction even though it never touches your actual in-game ping. Here are 12 resolvers worth testing, each with a distinct angle.

Cloudflare DNS leans on a distributed cache and global anycast network built for low-latency cache hits. Google Public DNS trades some of that speed edge for broad compatibility and a stable, mature global footprint. Quad9 blocks known malicious domains while keeping lookup times competitive, which suits anyone who wants security without a noticeable performance cost. NextDNS gives you per-device filtering profiles if you want granular control over what resolves and what doesn't. OpenDNS has offered enterprise-style filtering and uptime for years, making it a safe pick for shared home networks. AdGuard DNS blocks ads and trackers at the resolver level, which can reduce background traffic during gameplay. DNS.Watch keeps things minimal with a no-logging policy for privacy-first users. NordVPN DNS bundles naturally with an existing VPN subscription. Mullvad Encrypted DNS pairs a strong privacy posture with DoH and DoT support. Comodo Secure DNS adds another layer of protection against malicious domains. Verisign Public DNS brings registry-grade operational stability. Control D (ControlD) offers configurable, user-controlled resolution profiles similar in spirit to NextDNS.

If you want the fastest likely lookup with minimal setup, start with Cloudflare or Quad9. If content filtering matters more than raw speed, NextDNS or OpenDNS give you more control. If you're already paying for a VPN, its bundled DNS is a reasonable default to test against the public options above.

The best DNS servers for gaming compared side by side — overview diagram

Does DNS actually change your gaming performance?

DNS only touches a narrow part of your connection: the moment your device looks up a server's address before a match starts, a patch downloads, or a CDN serves game assets. Once that lookup resolves and your game establishes a direct connection, DNS steps out of the picture entirely. It does not influence the in-game round-trip time you see in a ping meter during a match.

Where DNS does matter:

  • Login and authentication screens, which often query multiple domains before letting you into a game.
  • Matchmaking handshakes, which can stall briefly if the resolver is slow or unreachable.
  • Patch and update downloads, where DNS picks which CDN edge server you connect to.

The bulk of that delay comes down to cache hits versus cache misses. A cached response can return in a few milliseconds, while a miss forces the resolver to walk the delegation chain from root servers down to the authoritative one. Cache misses are the dominant source of DNS latency, and that penalty matters more for gaming than raw resolver speed on paper. EDNS client subnet behavior also plays a role: it helps resolvers direct you to a nearby CDN edge, which can shave real time off a patch download even though it won't touch your match latency.

How to test DNS latency from your own location

Resolver benchmarks published online rarely match what you'll see on your own network, because routing and peering vary by ISP and region. Testing locally takes a few minutes and gives you a real answer.

  1. Run a browser-based DoH benchmark that queries several resolvers from your current connection.
  2. Run a native lookup test using a tool like dig or dnsping for a second data point outside the browser.
  3. Warm up each resolver with a few throwaway queries before timing, so the first-connection handshake doesn't skew your results.
  4. Run at least 10 to 20 queries per resolver and record the median, minimum, maximum, and any failures.
  5. Repeat with both cached domains (sites you've already visited) and fresh, unique subdomains to separate warm-hit speed from cold-miss speed.

While you're at it, a speed test that reports DNS resolution time alongside latency and jitter gives you a fuller picture in one pass, since gaming performance depends on more than just the resolver. Browser-based DoH benchmarks run entirely on your device, so there's no server-side collection skewing your numbers.

Tools worth using: a browser DoH benchmark extension, a dig or dnsping script if you're comfortable with a terminal, and a dedicated DNS speed site for a second opinion.

Pro Tip: Test at the same time of day you usually play, since network congestion shifts resolver performance throughout the day.

How to change your DNS on PC, console, and router

Once you've picked a resolver, applying it takes a few minutes on most devices.

  1. Windows: open Network Settings, select your adapter's properties, and manually set the IPv4 and IPv6 DNS addresses to your chosen resolver.
  2. macOS: go to System Settings, select your network interface, and add the resolver's addresses under DNS.
  3. PS5 or Xbox: open network settings, choose manual IP configuration, and enter the primary and secondary DNS addresses.
  4. Router: log into the admin panel and set the DNS servers under DHCP settings so every device on the network inherits the change automatically.

After changing it, verify the switch worked with a quick lookup tool or by rerunning your benchmark.

  • Router-level changes cover every device on your network, which is simpler than configuring each console and PC separately.
  • DoH and DoT clients encrypt the lookup itself, which some routers and operating systems support natively and others require a third-party app for.
  • If only one device needs a different resolver (a gaming PC, say), set it there instead of at the router to avoid affecting the rest of the household.

Choosing the right DNS for your setup: a quick checklist

Speed on a benchmark chart means little if the resolver drops queries under load or routes you somewhere distant. Work through this checklist before settling on one:

  • Median lookup latency from your own test, not a published benchmark.
  • Failure or timeout rate across repeated queries, since a resolver that's fast but flaky will cause intermittent stalls.
  • Protocol support for DoH, DoT, or DoQ if encrypted lookups matter to you.
  • Privacy policy summary, especially if you'd rather your ISP or resolver not log your browsing patterns.
  • Security filtering, useful if you want malware domains blocked automatically, but worth testing against your actual game clients first.

Watch for red flags: consistent packet loss or timeouts during testing, routing that sends you to a distant data center despite nearby options, or aggressive content filtering that accidentally blocks a game's own domains. If you're on a shared or family network, a resolver with built-in filtering like OpenDNS or Quad9 is often worth the small trade-off in raw speed.

Pro Tip: If two resolvers post nearly identical latency, pick the one with the privacy policy you're more comfortable with rather than chasing a one-millisecond difference.

How GrandSpeed measures DNS performance for gaming

Our speed test reports DNS resolution time alongside download and upload speed, latency, jitter, packet loss, and bufferbloat, so you can see how your resolver choice fits into the rest of your connection instead of testing it in isolation.

  • DNS resolution time shows how long lookups take on your current resolver, right now, from your actual network.
  • Jitter and packet loss matter for voice chat and real-time matchmaking traffic, which a DNS-only test won't reveal.
  • Bufferbloat can mask or exaggerate perceived lag independent of your resolver, so checking it alongside DNS avoids chasing the wrong fix.

To use it for resolver comparison: run the test once on your current DNS setting, switch resolvers using the steps above, then run it again and compare the DNS resolution time field between runs. Three or four runs per resolver, at different times of day, gives you a more reliable picture than a single pass.

Is tuning your DNS worth the effort?

If you play competitively and shave milliseconds wherever you can, testing two or three resolvers takes fifteen minutes and occasionally pays off at login and matchmaking. If you play casually, you likely won't notice the difference. Either way, measure before you decide. A guess dressed up as a setting change isn't an improvement.

— Peter D

Put your DNS choice to the test

We built our speed test to show you more than a single download number, including the DNS resolution time that tells you whether your new resolver is actually faster on your network. Running it before and after a DNS change takes a couple of minutes and replaces guesswork with an actual reading.

Grandspeed

Benchmark your current resolver now at Grandspeed before switching to anything new.

FAQ

Is 8.8.8.8 or 1.1.1.1 better for gaming?

Neither is universally faster: Google's 8.8.8.8 and Cloudflare's 1.1.1.1 both run large, stable global networks, but which one resolves faster depends on your ISP's routing and your physical distance from each provider's nearest data center. Independent testing has even found other resolvers beating both in specific locations, which is why a local benchmark matters more than a general reputation.

Is 1.1.1.1 still the fastest DNS option?

Cloudflare's 1.1.1.1 remains a strong performer thanks to its distributed caching and conductor logic designed to minimize cache-miss penalties, but "fastest" depends on your network. Test it against Quad9 and Google Public DNS from your own connection rather than assuming it wins everywhere.

Is 9.9.9.9 good for gaming?

Quad9's 9.9.9.9 blocks known malicious domains while keeping lookup times competitive with other major public resolvers, based on its forwarder best-practices documentation. It's a solid pick if you want security filtering without a noticeable speed trade-off, though you should still confirm performance on your own network.

Is DNS 1.1.1.1 good for gaming?

Yes, Cloudflare's 1.1.1.1 is a reasonable default for gaming thanks to its global anycast network and cache-hit focus, but it only affects lookups like login and matchmaking rather than your actual in-game ping. Run a local test to confirm it outperforms alternatives like Quad9 or Google Public DNS on your specific connection.

Sources