dhcpd3rc10 not able to update zone
Willis L. Sarka
wlsarka at the-republic.org
Fri Jul 27 18:19:09 UTC 2001
Greetings,
I sent out an e-mail asking for some help about a week ago, but haven't
heard anything, so I figured I'd send out another call for help and cc the
bind-users mailing list as well. Any help is greatly appreciated.
Problem:
the dhcp server (running v3rc10) is getting a "not authorized" when trying
to perform a DDNS update:
Jul 27 02:45:38 homer dhcpd: if IN A lappy.boulder.emperative.com domain
doesn't exist add 21600 IN A lappy.boulder.emperative.com 172.16.1.220 add
21600 IN TXT lappy.boulder.emperative.com
"000428687575bb805bcd4e248431cc4bac": not authorized.
I can perform an update, by hand, using nsupdate, and that works. I am
using the insecure "allow-update" methodology for the zone - here is what
the configuration of that zone looks like from named.conf:
zone "boulder.emperative.com" IN {
type master;
file "db.boulder.emperative.com";
allow-update { "boulder-trusted"; };
allow-transfer { "all"; };
};
My dhcpd.conf file:
authoritative;
ddns-update-style interim;
ddns-domainname "boulder.emperative.com";
ddns-rev-domainname "in-addr.arpa";
ddns-updates on;
ignore client-updates;
option domain-name "boulder.emperative.com";
option domain-name-servers 172.16.0.5;
option routers 172.16.0.254;
option broadcast-address 172.16.1.255;
option subnet-mask 255.255.254.0;
#option netbios-name-server 172.16.0.6;
#option netbios-node-type 8;
default-lease-time 604800;
max-lease-time 1209600;
subnet 172.16.0.0 netmask 255.255.254.0 {
range 172.16.1.1 172.16.1.222;
}
More information about the bind-users
mailing list