Stops doing reverses for a few hours

Tuc tuc at ttsg.com
Mon Oct 6 14:40:35 UTC 2003


> 
> In article <bln51n$1erc$1 at sf1.isc.org>, Tuc  <tuc at ttsg.com> wrote:
> >	We have had a few servers that just seem to stop doing reverse
> >lookups for a few hours for all IPs in our netblock that aren't in cache.
> 
> My guess is that something is blocking the 215.231.105.163 server from
> talking to the authoritative servers for your reverse domain.  Maybe
> there's a packet filter somewhere, or an allow-query statement on the
> servers.
> 
	(216.231.105.163).

	That would make sense, but the first authoritative server is 
216.231.111.14, in the same /19 and the second is 209.51.161.86 which is
offsite. We have checked all packet filers and allow-query and it should
not be a problem. PLUS, the 2nd major time it happened, it stopped almost
exactly 4 hours after it started with NO changes anywhere in our 
configurations or network.

	When you did an nslookup, it said there was a timeout and then fell
over to the second server in the resolv.conf, which, coincidentally, its
216.231.111.14 .

		Tuc/TTSG Internet Services, Inc.


More information about the bind-users mailing list