secondary dns acting up

Thomas von Hassel t at garbage.dk
Tue Sep 19 12:11:57 UTC 2000


on 19/09/00 14:08, Mark.Andrews at nominum.com at Mark.Andrews at nominum.com
wrote:

> 
>> 
>> on 19/09/00 13:27, Mark.Andrews at nominum.com at Mark.Andrews at nominum.com
>> wrote:
>> 
>>> 
>>> If you have a old enough version this could be the problem.
>>> 
>>> 433.   [bug]           req_notify required the slave zone to have been load
>> ed.
>>> this may not be the case when a zone has expired or
>>> is being established over a dial on demand link.
>> 
>> My BIND version: bind-8.2-6
> 
> Upgrade.  See the following for security reasons why.
> http://www.isc.org/products/BIND/bind-security-19991108.html
> 
> Also  8.2.1 contains this fix.
> 
> 698.   [bug]           res_notify() was rejecting valid NOTIFY messages.
> re-organise code so that logged messages are more
> appropriate.
> 
> Also cut and paste the error messages.  It can be amazing what is
> just over looked, specially typos.


Im trying now the set up another slave dns. With bind 8.2.2-P5. Still the
same errors.

U dont have to specify the slave dns servers other that in named.soa or am i
wrong there ?

/thomas




More information about the bind-users mailing list