When a game launcher hangs on “connecting,” matchmaking fails to find servers, or a storefront loads at a crawl, a stale DNS cache is a frequent and easily fixed cause. Your PC keeps a local list of domain-name lookups to save time, but when those entries go out of date or get corrupted, connections break in confusing ways. Flushing the cache is a 10-second task that resolves a lot of “the internet works but the game does not” moments.
What the DNS cache does
Every time your PC contacts a server by name, it looks up the numeric IP address and stores the result locally so the next request is faster. Game services run on large, changing fleets of servers, so an IP your PC cached yesterday may be dead today. When that happens the launcher tries an address that no longer answers, and you get timeouts even though your connection is perfectly healthy.
| Symptom | DNS-related? | Quick action |
|---|---|---|
| Launcher stuck “connecting” | Often | Flush DNS, retry |
| Store pages load slowly | Often | Flush DNS, change resolver |
| Can browse web but not sign in | Sometimes | Flush DNS, check firewall |
| In-match lag/rubber-banding | No | Check packet loss/ping instead |
Flush the cache step by step
Windows
Open Command Prompt or PowerShell as administrator and run ipconfig /flushdns. You will see “Successfully flushed the DNS Resolver Cache.” For stubborn cases, follow with ipconfig /registerdns, then ipconfig /release and ipconfig /renew to refresh your IP lease as well. Restart the game launcher afterward so it makes fresh lookups.
Clear the browser and launcher too
Some launchers embed a browser with its own cache. If a storefront still misbehaves after a system flush, clear the launcher’s cache from its settings or fully close and reopen it. Chromium-based browsers also keep an internal DNS cache you can clear from their net-internals page.
Go further with a faster resolver
If flushing helps but slow lookups keep returning, your ISP’s default DNS server may be slow or unreliable. Switching to a reputable public resolver often shaves lookup times and improves reliability. Popular options resolve in the low single-digit milliseconds versus 20-50 ms for some ISP defaults, which makes launchers and stores feel snappier.
Set it on the adapter or the router
You can change DNS on the Windows network adapter properties, or set it once on your router so every device benefits. After changing resolvers, flush the cache again so old entries do not linger. Note that DNS only affects connecting and finding servers; it has no effect on in-match latency once you are already connected.
When DNS is not the culprit
If the flush does not help, the problem is elsewhere. In-game lag, rubber-banding, and warping are latency and packet-loss issues, not DNS. Sign-in failures can also come from an overzealous firewall or antivirus blocking the launcher. Rule DNS in or out first because it is so quick, then move on to those.
Watch for a poisoned or misconfigured hosts file
Beyond the cache, Windows checks a local hosts file before doing any DNS lookup. “Optimizer” tools, ad blockers, or old tweak guides sometimes add game or launcher domains to that file, pointing them at dead addresses and breaking connections in a way no flush will fix. If flushing and changing resolvers do not help a specific launcher, inspect the hosts file for entries mentioning that service and remove any you did not add deliberately. A clean hosts file with only the default commented lines ensures your resolver, not a stale override, is what decides where the launcher connects.
FAQ
Does flushing DNS improve my in-game ping?
No. DNS is only used to translate names to addresses when you first connect or find servers. Once you are in a match, your ping depends on the route and distance to the game server, not on your DNS cache. Flushing helps connection and matchmaking issues, not in-match lag.
How often should I flush the DNS cache?
Only when you hit a connection problem. There is no benefit to flushing on a schedule, since the cache exists to speed things up. Reach for it when a launcher or store misbehaves, or right after you change DNS servers.
Bottom line
A stale DNS cache produces classic “cannot connect” symptoms while the rest of your internet works fine. Run ipconfig /flushdns, restart the launcher, and if slow lookups persist, switch to a faster public resolver on your adapter or router. Just remember it fixes connecting and matchmaking, not the latency you feel once a match has started.
