peculiar lookup timeouts

[Blair Copeland]

I had pretty severe problems until I updated the Root B server, it
changed recently.

But I am still having a problem with Debian 2.6 and the Bind9 server.

I am having to downgrade to Debian 2.4 to get rid of a timout that hits
the first lookups.


Blair Copeland                                        Ph# (940) 565-4180
Communications Manager                                FAX (940) 565-4060
Network Operations and Services	                      TTY (800) RELAY TX
Data Communications                                   noc.unt.edu/~copeland
Computing and Information Technology Center           copeland at unt.edu


On Wed, 13 Sep 2006, Adam Young wrote:

> Date: Wed, 13 Sep 2006 14:21:26 -0400
> From: Adam Young <adamy at mountaincable.on.ca>
> To: comp-protocols-dns-bind at isc.org
> Subject: RE: peculiar lookup timeouts
> 
> Hi Shaheen,
>
> Yes, sorry.  I also get "SERVFAIL" until I restart bind.  I just looked at
> my notes again from the last time I encountered the problem.
>
> If anyone else has come across this and has any answers, I'd like to avoid
> downgrading to Bind8 if possible.
>
> Thanks,
>
> -
> Adam Young
> Systems Support Technologist
> Mountain Cablevision Ltd.
> (905)667-7436
>
>
>> -----Original Message-----
>> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
>> Behalf Of Shaheen
>> Sent: Wednesday, September 13, 2006 1:02 PM
>> To: comp-protocols-dns-bind at isc.org
>> Subject: Re: peculiar lookup timeouts
>>
>>
>> Adam Young wrote:
>>> Hey guys,
>>> Running Bind-9.3.2P1, three servers: ns1(master) ns2,ns3(slaves).  Every
>>> once in a while a customer will call in saying that they cannot resolve
>> a
>>> particular domain.
>>
>> Am having the very same problem and also when i restart named
>> everything returns to normal.
>> i figured it was becuase the PIX firewall ASA which blocks queries
>> bigger than 512 but even removing that rule didn't work.
>> now I temporarly configured a BIND 8 server and forwarded public DNS
>> servers to it.
>> anyway my error is server failed not timed out
>
>
>
>

Blair Copeland                                        Ph# (940) 565-4180
Communications Manager                                FAX (940) 565-4060
Network Operations and Services	                      TTY (800) RELAY TX
Data Communications                                   noc.unt.edu/~copeland
Computing and Information Technology Center           copeland at unt.edu