The best DNS server for gaming isn't the one with the lowest number in an ad — it's the one that answers consistently, every time, so nothing stalls right before a match or a patch download.
What is the best DNS for gaming?
A gaming DNS setup is really just a fast, low-jitter public resolver — such as Cloudflare (1.1.1.1) or Google (8.8.8.8) — used to shorten the lookup delay before your game's launcher, matchmaking, or patch servers connect. It does not reduce in-match ping, which is controlled by the route to the game server, not DNS.
Each resolver is queried 8 times (plus 2 warm-up, excluded) — more lookups give a steadier, more accurate median but take longer. Measures 34 resolvers in your browser: verified where the resolver allows it, otherwise an approximate round trip.
Runs entirely in your browser. We measure how quickly each resolver answers a fresh lookup over encrypted DNS-over-HTTPS — no downloads, no account, nothing stored.
It helps to separate two things that get conflated: the one-time lookup that happens before you connect, and the ongoing connection while you play.
Once your game client has resolved a hostname to an IP address and opened a connection, DNS is out of the picture entirely — the game talks directly to that IP for the rest of the session. A faster resolver shortens the small delay at the start of a connection; it does not change your download or upload bandwidth, and it can't fix a slow route to a distant game server.
Most DNS marketing leads with a headline speed. For gaming, that's the wrong number to chase. A resolver that is usually fast but occasionally spikes will produce the exact moment you notice — a stall right as your launcher tries to connect at the start of a session, or a patch server lookup that hangs for a second while everyone else in your party has already started downloading.
Jitter is the variation between lookups — essentially, how consistent a resolver is from one query to the next. A resolver with low jitter gives you roughly the same short delay every time, which is far less noticeable than an occasional long one. When comparing resolvers on the benchmark page, weight jitter and reliability alongside the median, not just whichever number is smallest.
These are qualitatively strong picks for the combination gaming benefits most from: consistent latency and high reliability. Exact numbers vary by network, so use the test above to confirm which is actually fastest and steadiest for you.
Cloudflare
The fastest major resolver on most connections, with a strong no-logging privacy stance and no default filtering.
1.1.1.1 1.0.0.1 
A globally distributed, extremely reliable resolver. Uses EDNS Client Subnet, which helps CDN routing at a small privacy cost.
8.8.8.8 8.8.4.4 
Quad9 Foundation
A security-first non-profit resolver that blocks known malicious domains and keeps no source-IP logs.
9.9.9.9 149.112.112.112 Avoid resolvers with heavy content filtering if you want the fewest extra milliseconds per lookup — filtering adds a small amount of processing on the resolver's side. If you also want ad or malware blocking, that trade-off is usually worth it; see AdGuard DNS or Quad9 for filtered options.
You can set DNS on the device running the game, or once on your router so every console and PC on your network benefits. Router-level changes are the simplest way to cover a shared gaming setup.
No. In-game ping is the round trip between your device and the game server over the game's own connection, and DNS has no part in that path once the connection is open. A gaming-friendly DNS resolver can only shorten the lookup that happens before that connection starts.
It shortens the delay before your game client connects to matchmaking, login, or patch-download servers — the moment you see a loading spinner while the game resolves a hostname. A consistent, low-jitter resolver also means that delay doesn't randomly spike between sessions.
For the DNS step, yes. A resolver that answers in a fairly stable 15–20 ms every time is more useful than one that sometimes answers in 5 ms but occasionally takes 150 ms. Predictability avoids the rare, jarring stall right as a match is starting or a patch server needs to be reached.
Marketing aside, a DNS resolver cannot reduce lag inside an established game connection — that route is fixed by your ISP's path to the game server, not by DNS. Any DNS provider that is fast and consistent for lookups will do the DNS part equally well; what differs between providers is filtering, privacy, and reliability, not in-match latency.
ISP resolvers vary widely in speed and consistency, and some throttle or redirect certain requests. A well-run public resolver is usually at least as fast and more predictable, plus you gain a clear privacy policy. Run the test below on your own connection to see which is actually faster for you.