Demystifying DNS Resolution Delays on Consumer ISP Routers
A common symptom misdiagnosed as "slow internet" is actually DNS resolution latency. When a user navigates to a website, the browser must resolve the domain to an IP address. If the ISP's default DNS servers are under heavy load or geographically distant, this lookup can add 100ms+ to every single web request. The Diagnostic Process To determine if DNS is the bottleneck, bypass the domain layer…
Many users experience what they think is slow internet when in reality the issue lies in DNS resolution latency. When a person visits a website, their browser needs to convert that domain name into an IP address. If the Internet Service Provider's default DNS servers are either heavily used or far away, this lookup can add 100ms or more to every web request.
To check if DNS is the problem, bypass the domain layer. If directly entering an IP address like https://1.1.1.1 works quickly, but visiting https://google.com gets stuck on "Resolving host," then the local DNS cache or upstream forwarder might be malfunctioning. Many consumer routers intercept port 53, making all devices on the LAN use the ISP's slow resolvers.
In my upgrades for local businesses in Sunningdale, I set the main DHCP scope to provide high-speed, privacy-focused public resolvers such as Cloudflare's 1.1.1.1 and 1.0.0.1, and Quad9's 9.9.9.9 (which includes threat blocking).
To confirm which server is handling the queries, use nslookup: type "nslookup google.com." If the response points to your local router gateway (like 192.168.1.1), the router is forwarding the requests. For the router to function correctly, it must pass the upstream DNS addresses directly to the client devices through DHCP. For more details on establishing reliable baseline metrics for troubleshooting, check out my guide on FTTP Latency Baselines.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
