Google public DNS flapping/non-functional

[Blair Trosper]

Could someone from Google contact me off list to discuss the public
resolvers?

I'm getting NXDOMAIN and then a proper response literally one second later.
 And from there it's just 20 GOTO 10...the resolver seems to be having a
psychotic episode, or...at the very least...an identity crisis.

Other public resolver services have no issue with this, but the problem
seems to be affected by anything I throw at either 8.8.8.8 or 8.8.4.4 to
resolve.

(The IPv6 public resolvers are doing the same thing, I should point out.)

I understand that those ingress addresses are any/multicast, so perhaps the
problem I'm having is confined to a single datacenter in my region...and
thus may not be affecting people outside of that DC.

Thanks,
Blair

Re: Google public DNS flapping/non-functional

[Casey Deccio]

On Thu, Mar 28, 2013 at 11:51 AM, Blair Trosper blair.tros...@gmail.comwrote:

 Could someone from Google contact me off list to discuss the public
 resolvers?

 I'm getting NXDOMAIN and then a proper response literally one second later.
  And from there it's just 20 GOTO 10...the resolver seems to be having a
 psychotic episode, or...at the very least...an identity crisis.


These symptoms have been seen on DNSSEC validating resolvers when they
encounter a signed zone that is misconfigured.  Google has recently begun
DNSSEC validation, so it could very well be related, depending the
configuration of the zone in question, including whether or not it is
signed, and Google's resolver/validator implementation.

Casey