4 ms·
I wish 10 minutes was the minimum acceptable TTL, that'd be tremendous progress already. It's typically much more than 1 round trip, given typical amount of cr
by meltedcapacitor 6y ago
I wish 10 minutes was the minimum acceptable TTL, that'd be tremendous progress already.
It's typically much more than 1 round trip, given typical amount of crap frameworks and gadgets that each load themselves and dependencies from around the world on a typical webpage. On a page that takes 50 seconds to load all the crap from 50 servers each with a 5 second TTL through a flaky ISP DNS server, you get hit all the time basically.
200ms is not worst case, that's more like median, worst case is DNS being stuck for minutes with responses lost or very slow (say 20 seconds). Often DNS is the only thing that's broken, and if you're in one session (with no new DNS request required beyond refreshes from expired TTL) it makes the difference between the user being stuck or being able to proceed unhindered, until they go to a new site requiring a new request.
- znpy 6y agoThe only time I've seen DNS failing after seconds, about six seconds iirc, was when an host had three DNS server configured, all of which were wrong (public DNS servers, used to query an internal zone). It took seconds for the request to time out because the host tried all three records one after another, and gave up only when all three had failed. But, uh, that's an uncommon situation.