Re: Intermittent incorrect DNS resolution?
erik.levinson at uberflip.com
Thu Jan 17 04:09:39 UTC 2013
Thanks Joe and thanks everyone else for the on and off-list replies. Quite insightful.
I think we've reached the consensus that the problem is the ignoring of TTLs as opposed to misbehaving/stale authoritative servers. So for now I shall wait.
To give an idea of the scale of the problem right now, I'm getting thousands of requests per minute to a new IP vs. about two requests per minute on the equivalent old IP, with over 60% of the latter being Baidu, but also a bit of Googlebot and other random bot and non-bot UAs.
Perhaps next week I'll unbind some old IPs for a few minutes to see what happens.
From: "Joe Abley" <jabley at hopcount.ca>
Sent: Wednesday, January 16, 2013 8:57pm
To: "Erik Levinson" <erik.levinson at uberflip.com>
Cc: "Christopher Morrow" <morrowc.lists at gmail.com>, nanog at nanog.org
Subject: Re: Intermittent incorrect DNS resolution?
On 2013-01-16, at 14:33, Erik Levinson <erik.levinson at uberflip.com> wrote:
> True...I did try 126.96.36.199 / 188.8.131.52 and some local ones here. All looked fine.
I sent queries from 270+ different locations for the domains you mentioned off-list and I didn't see any inconsistencies. The persistent host-caching/browser-caching theories seem like your best bet (or my 270+ locations weren't sufficiently diverse to catch a stale zone being served by an anycast authority server).
More information about the NANOG