[122270] in North American Network Operators' Group
Re: Connectivity problems to google via openDNS
daemon@ATHENA.MIT.EDU (David Ulevitch)
Wed Feb 10 17:16:06 2010
Date: Wed, 10 Feb 2010 14:14:13 -0800
From: David Ulevitch <davidu@everydns.net>
To: nanog@nanog.org
In-Reply-To: <20100209234316.GQ16972@hezmatt.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 2/9/10 3:43 PM, Matthew Palmer wrote:
> Turned out that the DNS responses from OpenDNS (they were in a
> cafe somewhere with free wireless that was using OpenDNS) were giving
> slightly wrong addresses -- like the real address for example.com was
> 192.0.2.12, and OpenDNS was giving the response that example.com was at
> 192.0.2.16 (another server in the same cluster, hence the insane confusion).
> No wildcarding or recent DNS changes at our end, either -- it was just
> OpenDNS screwing things up *somehow*.
I've never heard of such a report until now. And if true, that would be
shockingly bizarre behavior. In the past when I've heard similar, I
have a 100% success rate in discovering it's actually a misconfiguration
of authoritative records.
Feel free to email me directly if you ever find yourself encountering a
similar situation like that again and I'll be happy to troubleshoot it.
Thanks,
David
