DNS update -- reverse zone
Chris Buxton
cbuxton at menandmice.com
Mon Sep 18 21:53:17 UTC 2006
Either the DHCP server isn't presenting the correct key when updating
the reverse zone, or else named is rejecting this name:
220.1.168.192.1.168.192.in-addr.arpa
You might need to configure dhcpd to use the correct reverse zone
name. It looks like a mix-up involving the origin.
Chris Buxton
Men & Mice
Take control of your network
On Sep 18, 2006, at 8:36 AM, Joe Terry wrote:
> I am trying to get dynamic updating working. It will update the
> forward
> zone, but not the reverse! The named.conf file is basically the
> same for
> both. Here is the data:
>
> Error message
>
> Sep 17 21:50:16 localhost named[4187]: client 127.0.0.1#32874:
> updating zone
> 'auto-sci.jdt/IN': adding an RR
> Sep 17 21:50:16 localhost named[4187]: client 127.0.0.1#32874:
> updating zone
> 'auto-sci.jdt/IN': adding an RR
> Sep 17 21:50:16 localhost named[4187]: journal file
> /etc/bind/zones/db.auto-sci.jnl does not exist, creating it
> Sep 17 21:50:16 localhost named[4187]: zone auto-sci.jdt/IN: sending
> notifies (serial 2006091712)
> Sep 17 21:50:16 localhost dhcpd: Added new forward map from
> Rosanne.auto-sci.jdt to 192.168.1.220
> Sep 17 21:50:16 localhost named[4187]: client 192.168.1.170#32874:
> update
> '1.168.192.in-addr.arpa/IN' denied
> Sep 17 21:50:16 localhost dhcpd: unable to add reverse map from
> 220.1.168.192.1.168.192.in-addr.arpa to Rosanne.auto-sci.jdt: timed
> out
>
> named.conf.local
> include "/etc/bind/rndc.key";
>
> zone "auto-sci.jdt" in {
> type master;
> file "/etc/bind/zones/db.auto-sci";
> allow-update { key "rndc-key"; };
> };
>
> zone "1.168.192.in-addr.arpa" in {
> type master;
> file "/etc/bind/zones/db.192.168.1";
> allow-update { key "rndc-key"; };
> };
>
>
>
> Does anyone have an idea?
>
>
>
>
>
More information about the bind-users
mailing list