Spotty Lookups on One of Our Networks
Barry Margolin
barmar at alum.mit.edu
Wed Oct 31 17:48:47 UTC 2012
In article <mailman.544.1351690146.11945.bind-users at lists.isc.org>,
Carsten Strotmann <cas at strotmann.de> wrote:
> Hello Martin,
>
> Martin McCormick <martin at dc.cis.okstate.edu> writes:
>
> > I described a case where one of our remote campuses can't
> > resolve a number of remote domains. One example is noaa.gov. It
> > also successfully resolves random remote domains without
> > seemingly any rime or reason.
> >
> > Here is a bad dig trace for noaa.gov
> >
> [...]
>
> <http://www.zonecut.net/dns> shows that
> nameserver ns-e.noaa.gov is not responding
>
> The dig +trace might "hang" if that authoritative DNS server is selected
> for the query.
>
> "ns-mw.noaa.gov" and "ns-nw.noaa.gov" operate fine. "ns-e" could mean
> "east coast".
Did the problem coincide with Hurricane Sandy? That would explain
inability to reach many east coast servers. Resolvers should work around
this by failing over to other servers (assuming the organization has
them geographically distributed, as NOAA.GOV does), but dig +trace
doesn't.
--
Barry Margolin
Arlington, MA
More information about the bind-users
mailing list