News for hackers. Stuff that matters.
Re:Network Solutions' DNS was down by colmmacc on Wednesday July 17, 2013 @11:12AM (#6058107)
(I work on Route 53).

We've done a lot of experiments on this one and we've found that the most common resolvers make 3 tries to 3 different servers by default. At first those servers are picked at random, but over time the resolvers usually "home in" on what the least-latent nameserver is. Once they do, and have a good round-trip-time estimate for how long it takes to respond, they stay using it. But they have a hair-trigger; if the nameserver doesn't respond, they'll very quickly fall-back to trying the other nameservers.

In practice what that means is that up to two of your nameservers may be completely unresponsive and the effects will be pretty negligible. So if you're using multiple DNS providers and want to protect against one going off-air; use no more than two nameservers from each provider.

That said, for all of the reasons above, and some more, the Route 53 SLA currently only applies if you use all four Route 53 nameservers.

Re:Network Solutions' DNS was down by mmmooo on Wednesday July 17, 2013 @11:18AM (#6058142)
Any thoughts on where/how is this 'home in' state is saved? Other the cache and filtering/acl state resolvers should be stateless, so would be interested in any details, especially if this is on a per-zone, or per-set of nameservers or etc basis. I've never seen bind9 act like this.
Re:Network Solutions' DNS was down by colmmacc on Wednesday July 17, 2013 @11:23AM (#6058177)
I haven't read the bind source in a long time, but my best guess is that it's in memory.

http://docstore.mik.ua/orelly/networking_2ndEd/dns/ch02_06.h...

Has some details, and I believe Bind and PowerDNS call it "Smoothed RTT" or SRTT.

Re:Network Solutions' DNS was down by mmmooo on Wednesday July 17, 2013 @11:32AM (#6058244)
interesting, not a ton of details of how. off to the source I go, thanks. sounds like it assigns a 'score' of some sort to each authoritative ns.
Re:Network Solutions' DNS was down by isb on Wednesday July 17, 2013 @02:23PM (#6059282)
This might help - section 4.4 has formal details on the Bind server selection algorithms: http://ocw.mit.edu/courses/mathematics/18-996-topics-in-theo...
Re:Network Solutions' DNS was down by mmmooo on Wednesday July 17, 2013 @03:28PM (#6059690)
yep definitely, an interesting implementation, and certainly almost impossible to guess from passive observation. thanks.
Re:Network Solutions' DNS was down by dsl on Wednesday July 17, 2013 @01:00PM (#6058752)
BIND assigns a score based on every IP it talks to and a hit rate. (so if ns1.foo.com resolves to 3 IPs, each is tracked individually, same if ns1.bar.com and ns1.baz.com are the same IP) It is a pretty small cache, maybe like 1024?

This is all from fuzzy 5 year old memory.