update failed: NOTZONE

Bind, PowerDNS
knebb
Posts: 92
Joined: 2006-05-30 11:16
Location: M-V

update failed: NOTZONE

Post by knebb » 2007-09-23 18:02

Yohoo!
Habe eine kleine Sorge mit meinem dynamischen NS.
Nutze bind 9.x (von CentOS5)
Die named.conf enthaelt u.a.:

Code: Select all

zone "10.168.192.in-addr.arpa" in {
                type master;
                file "master/192.168.10";
                also-notify {192.168.10.2; 192.168.11.50; 192.168.11.1;};
                allow-update { key rndckey; key DHCP_UPDATES;};
        };

Dann habe ich eine update-ns.txt:

Code: Select all

server ns.my-domain.de
zone 0.168.192.in-addr.arpa
update delete 4 PTR
update add 4 86400 PTR mx.my-domain.de.
show
send

Rufe ich das Ganze nun mit

Code: Select all

nsupdate -k /etc/Kdhcp.....private -v update-ns.txt
Bekomme ich immer den gleichen Fehler:

Code: Select all

update failed: NOTZONE
:evil:
Habe schon gesucht, aber keine brauchbare Erklaerung gefunden. Jemand eine Idee?

Anonymous

Re: update failed: NOTZONE

Post by Anonymous » 2007-10-10 12:26

knebb wrote:Yohoo!
Dann habe ich eine update-ns.txt:

Code: Select all

server ns.my-domain.de
zone 0.168.192.in-addr.arpa
update delete 4 PTR
update add 4 86400 PTR mx.my-domain.de.
show
send


Try fully qualifying the domain names and let me know if that works:

Code: Select all

update delete 4.0.168.192.in-addr.arpa.
update add 4.0.168.192.in-addr.arpa. 86400 PTR mx.my-domain.de.


I've seen the same thing and am going to consult with the BIND gurus to see if this is a bug in nsupdate.

(Sorry, my German is lacking, replies in English would be appreciated)

Knobee

knebb
Posts: 92
Joined: 2006-05-30 11:16
Location: M-V

Re: update failed: NOTZONE

Post by knebb » 2007-10-10 14:27

Knobee wrote:Try fully qualifying the domain names and let me know if that works:

Code: Select all

update delete 4.0.168.192.in-addr.arpa.
update add 4.0.168.192.in-addr.arpa. 86400 PTR mx.my-domain.de.

Yepp, that works fine now. Thanks for the hint!

I've seen the same thing and am going to consult with the BIND gurus to see if this is a bug in nsupdate.

Wow. So some further information for reference:
CentOS5 i386
bind& bind-utils 9.3.3-9.0.1.el5

Thanks again& CU

Christian