Notify errors
Kevin Darcy
kcd at daimlerchrysler.com
Tue Oct 17 20:17:42 UTC 2000
Bug #1025: "NOTIFY messages should have AA". (Fixed in T6B). This problem has
probably been present all along, it just never generated any log messages
before.
Don't know about the IXFR problem. I haven't tested IXFR lately...
- Kevin
Walker, Rob wrote:
> Hi,
>
> Im runnig bind 8.2.3 T6B on Solaris 2.7 ...
>
> Notify messages are making it to the slave, however the slave never IXFR's.
> I'm recieving the following error message on the slave :
>
> 17-Oct-2000 09:58:18.930 notify: debug 1: FORMERR Notify request without AA
> ns_req: answer -> [192.57.30.5].1051 fd=22 id=47631 size=12 rc=1
> datagram from [192.57.30.5].1051, fd 22, len 34
>
> IXFR only works by forcing it with ndc reload inkok.us.eds.com
>
> Please Help :(
>
> My config follows:
>
> Master named.conf section
>
> options {
> directory "/var/named";
> maintain-ixfr-base yes;
> };
>
> server 192.57.31.5 {
> support-ixfr yes;
> };
>
> zone "inkok.us.eds.com" {
> type master;
> file "inkok.us.eds.com.db";
> allow-update { 192.57.30.5;};
> allow-transfer { 192.57.31.5; };
> notify yes;
> };
>
> ************************************************************
>
> Slave named.conf section:
>
> server 192.57.30.5 {
> support-ixfr yes;
> };
>
> zone "inkok.us.eds.com" {
> type slave;
> masters { 192.57.30.5; } ;
> file "inkok.us.eds.com.db.sec";
> check-names ignore;
> };
>
> Thank you !
>
> rob.walker at eds.com
More information about the bind-users
mailing list