Help! NOTZONE error with nsupdate

[Mark_Andrews at isc.org]

	Note also that this is undocumented behaviour in BIND 8.
	It will not be implemented in BIND 9.  The ppp implementation
	needs to be fixed.

	Mark
> 
> 	BIND 8's nsupdate sorted the updates into different zones.
> 	BIND 9's nsupdate does not do this.  The update below is
> 	trying to update two different zones.  Split the update
> 	with a blank line so it gets processed as two updates not
> 	one.
> 
> 	Mark
> 
> > 
> > Hi,
> > See the earlier thread with the same subject.
> > 
> > I now have all the recent versions.
> > Client: BIND 9.1.3 (from RPM, patch level 3)
> > Server: named 8.2.4-REL Thu Sep 20 20:01:26 CEST 2001 (compiled)
> > 
> > Still, this error appears in the servers log file trying to do a dynamic
> > zone update.
> > 20-Sep-2001 20:06:53.859 error processing update packet (NOTZONE) id
> > 20638 from [213.166.X.Y].1041
> > 
> > The nsupdate command is the following:
> > /usr/bin/nsupdate -k /var/named/keys/Kkey.+157.+00000.private
> > /etc/ppp/nsupd.cfg
> > 
> > nsupd.cfg contains
> > update delete access.lan.x.lu. A
> > update add access.lan.x.lu. 1 A 213.166.X.Y
> > update delete b.mx.x.lu. A
> > update add b.mx.x.lu. 1 A 213.166.X.Y
> > [blank line]
> > 
> > An extract from named.conf:
> > zone "mx.x.lu" {
> >         type master;
> >         file "name2ip/x.mx.lu";
> >         allow-update {
> >                 key key.;
> >         };
> > };
> > Same thing for lan.x.lu.
> > 
> > x.mx.lu contains this:
> > ;BIND DUMP V8
> > $ORIGIN x.lu.
> > mx      86400   IN      SOA     ns1.iip.lu. jmroth.iip.lu. (
> >                 2001081805 3600 1800 0 0 )      ;Cl=3
> >         86400   IN      NS      ns1.iip.lu.     ;Cl=3
> >         86400   IN      NS      ns2.iip.lu.     ;Cl=3
> > $ORIGIN mx.x.lu.
> > b       1       IN      A       213.166.X.Y   ;Cl=3
> > a       86400   IN      A       212.24.195.18   ;Cl=3
> > 
> > The primary domain (x.lu) has this setup:
> > $ttl    86400
> > @       IN      SOA     ns1.iip.lu.       jmroth.iip.lu. (
> >                         2001091001
> >                         8H
> >                         2H
> >                         1W
> >                         1D )
> >         NS      ns1.iip.lu.
> >         NS      ns2.iip.lu.
> >         MX      10      b.mx
> >         MX      20      a.mx
> > lan     NS      ns1.iip.lu.
> > lan     NS      ns2.iip.lu.
> > mx      NS      ns1.iip.lu.
> > mx      NS      ns2.iip.lu.
> > 
> > localhost       A       127.0.0.1
> > 
> > www     A       212.24.195.16
> > ftp     A       212.24.195.16
> > mail    CNAME   a.mx
> > pop     A       212.24.195.18
> > @       A       212.24.195.16
> > 
> > Before all this, I had Bind 8 on the client too and that worked
> > flawlessly.
> > 
> > Could it be that it doesn't like the ns1.iip.lu SOA?
> > Any other idea?
> > 
> > Regards.
> > jmr
> > 
> > 
> --
> Mark Andrews, Internet Software Consortium
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org
> 
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org