Re:Why HN Got Slow
by ComputerGuru on Wednesday August 10, 2011 @02:57AM
(#2867064)
That completely slipped my mind. You are, of course, correct.
An alternative suggestion here is to use Comcast's 75.75.75.75 IP address; while it may seem static, it's actually an anycast address, and will resolve to the nearest node.
One thing many people forget when choosing a DNS server is that it's not just the ping time that counts - the time it takes the server to reply to the actual DNS request is what matters.
e.g. while 75.75.75.75 for me (Comcast Chicago) is a 15ms trip and 8.8.8.8 is a 28ms ping, the lookup on the former (dig x.com @dns_ip) can reach 120ms while on Google's DNS it never exceeds ~35ms.
An alternative suggestion here is to use Comcast's 75.75.75.75 IP address; while it may seem static, it's actually an anycast address, and will resolve to the nearest node.
One thing many people forget when choosing a DNS server is that it's not just the ping time that counts - the time it takes the server to reply to the actual DNS request is what matters.
e.g. while 75.75.75.75 for me (Comcast Chicago) is a 15ms trip and 8.8.8.8 is a 28ms ping, the lookup on the former (dig x.com @dns_ip) can reach 120ms while on Google's DNS it never exceeds ~35ms.