Re: Spotty Lookups on One of Our Networks

2012-10-31 Thread Martin McCormick
The system hung long enough to have timed out on every possible DNS that it could have tried so it should have gotten to one. Barry Margolin writes: > Did the problem coincide with Hurricane Sandy? That would explain > inability to reach many east coast servers. Resolvers should work aroun

Re: Spotty Lookups on One of Our Networks

2012-10-31 Thread John Miller
Martin, what do you see if you do a packet capture on the host where you're running dig? How 'bout at the border of your network? Obviously traffic's not making it through, but where? Any sort of split routing paths that might be involved? John On Wed, Oct 31, 2012 at 8:54 AM, Martin McCormick

Re: Spotty Lookups on One of Our Networks

2012-10-31 Thread Barry Margolin
In article , Carsten Strotmann wrote: > Hello Martin, > > Martin McCormick 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

Re: Spotty Lookups on One of Our Networks

2012-10-31 Thread Carsten Strotmann
Hello Martin, Martin McCormick 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 n

Re: Spotty Lookups on One of Our Networks

2012-10-31 Thread Martin McCormick
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 ; <<>> DiG 9.7.7 <<>> @localhost +trace no

Re: Spotty Lookups on One of Our Networks

2012-10-30 Thread Mark Andrews
In message <201210302010.q9ukaytl064...@x.it.okstate.edu>, Martin McCormick wri tes: > I don't thing this is a bind problem because this > particular network has some Microsoft DNS's that are doing > exactly the same thing. > > There are several domains names that are broken in this >

Re: Spotty Lookups on One of Our Networks

2012-10-30 Thread Martin McCormick
John Miller writes: > Just to clarify, how many domain names are doing this for you? Are they > all > remote domains, or are some of them okstate.edu domains? They are all remote as far as I can tell. I will have some answers for Barry Margolin's questions a bit later. It seems like the tear of

Re: Spotty Lookups on One of Our Networks

2012-10-30 Thread John Miller
Hi Martin, Just to clarify, how many domain names are doing this for you? Are they all remote domains, or are some of them okstate.edu domains? John -- John Miller Systems Engineer Brandeis University johnm...@brandeis.edu On 10/30/2012 04:10 PM, Martin McCormick wrote: I don't thin

Re: Spotty Lookups on One of Our Networks

2012-10-30 Thread Barry Margolin
In article , Martin McCormick wrote: > I don't thing this is a bind problem because this > particular network has some Microsoft DNS's that are doing > exactly the same thing. > > There are several domains names that are broken in this > network and the symptome is always the same:

Spotty Lookups on One of Our Networks

2012-10-30 Thread Martin McCormick
I don't thing this is a bind problem because this particular network has some Microsoft DNS's that are doing exactly the same thing. There are several domains names that are broken in this network and the symptome is always the same: Dig +trace @localhost one.bad.domain.co