[162782] in North American Network Operators' Group
Re: Google Public DNS Problems?
daemon@ATHENA.MIT.EDU (Livingood, Jason)
Wed May 1 15:15:50 2013
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: Jared Mauch <jared@puck.nether.net>, Tony Finch <dot@dotat.at>
Date: Wed, 1 May 2013 19:13:22 +0000
In-Reply-To: <35EE6F61-6847-4CEF-B996-4BF5574C7BEF@puck.nether.net>
Cc: "nanog@nanog.org" <nanog@nanog.org>, "Ganster,
Chris" <Chris_Ganster@cable.comcast.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 5/1/13 2:23 PM, "Jared Mauch" <jared@puck.nether.net> wrote:
>On May 1, 2013, at 1:39 PM, Tony Finch <dot@dotat.at> wrote:
>>Blair Trosper <blair.trosper@gmail.com> wrote:
>>=20
>>> Goes all the way up to the A root server before failing spectacularly.
>>=20
>> That is an extremely weird response. Are you sure your queries are not
>> being intercepted by a middlebox? What happens if you use dig +vc ?
>> Do you get a similar round-trip time when pinging 8.8.8.8 to the one
>> reported by dig?
>
>Some places like Wayport/attwifi intercept all udp/53 traffic and direct
>it to their local server. You won't notice this with a ping, but you
>will see it in the 0 or 1ms reply :)
FWIW, no DNS intercepts happen on the Comcast network=8A
Jason (Comcast)
