[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Google Public DNS Problems?
- Subject: Google Public DNS Problems?
- From: jra at baylink.com (Jay Ashworth)
- Date: Thu, 2 May 2013 11:51:12 -0400 (EDT)
- In-reply-to: <[email protected]om>
----- Original Message -----
> From: "Christopher Morrow" <morrowc.lists at gmail.com>
> On Thu, May 2, 2013 at 10:32 AM, Jay Ashworth <jra at baylink.com> wrote:
> > ----- Original Message -----
> > > From: "Perry Lorier" <isomer at gmail.com>
> > > On 5/1/13 12:38 PM, Blair Trosper wrote:
> > >
> > > > That's all well and good, but I certainly wouldn't expect "nslookup
> > > > gmail.com <http://gmail.com>" or for "nslookup google.com" to
> > > > return SERVFAIL
> > > Do you have traceroutes to 220.127.116.11 and 18.104.22.168?
> > Is that actually pertinent?
> > 8.8 and 8.4 aren't *public zone servers* for Google's commercial domains,
> > are they? I have been assuming they were only open recursive resolver
> > nameservers...
> I think perry's question is: "Can you show me which networks you traversed
> and which instance of the service you were talking to at the time of
> the problem?" (or 'now' if the problem is persisting)
But since Perry's problem is *inability to resolve names in google's
public zones*, the *path to the ZONE servers* is the thing diagnostics
would require a trace to, no?
If 22.214.171.124 doesn't *answer* for "google.com" (and no one's told me it
has), then how you get there is irrelevant.
Jay R. Ashworth Baylink jra at baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA #natog +1 727 647 1274