I have a local zone which is updated by a DHCP server.
I'm using a bind 9.4.2 and a dhcpd 3.0.
The updates are working great, I 'm able to add remove machines and
reverses in the local zone.
However, each time I restart the named daemon, it complains that the
zone contains out-of-zone data.
Here's an extract
Sep 4 11:40:46 bigboss named[17881]: zone local.foo.org/IN: loaded
serial 2007104284
Sep 4 11:40:46 bigboss named[17881]: /etc/bind/db.local:3: ignoring
out-of-zone data (local.toto.fr)
Sep 4 11:40:46 bigboss named[17881]: /etc/bind/db.local:23: ignoring
out-of-zone data (admporgi.local.foo.org)
Sep 4 11:40:46 bigboss named[17881]: /etc/bind/db.local:24: ignoring
out-of-zone data (admzerlinda.local.foo.org)
Sep 4 11:40:46 bigboss named[17881]: /etc/bind/db.local:25: ignoring
out-of-zone data (aida.local.foo.org)
Sep 4 11:40:46 bigboss named[17881]: /etc/bind/db.local:27: ignoring
out-of-zone data (altoum.local.foo.org)
Sep 4 11:40:46 bigboss named[17881]: /etc/bind/db.local:28: ignoring
out-of-zone data (alvaro.local.foo.org)
Sep 4 11:40:46 bigboss named[17881]: /etc/bind/db.local:30: ignoring
out-of-zone data (Amazone.local.foo.org)
Sep 4 11:40:46 bigboss named[17881]: /etc/bind/db.local:33: ignoring
out-of-zone data (apc.local.foo.org)
Sep 4 11:40:46 bigboss named[17881]: /etc/bind/db.local:34: ignoring
out-of-zone data (aramis.local.foo.org)
Sep 4 11:40:46 bigboss named[17881]: /etc/bind/db.local:36: ignoring
out-of-zone data (arlequin.local.foo.org)
Sep 4 11:40:46 bigboss named[17881]: /etc/bind/db.local:38: ignoring
out-of-zone data (Arpagon.local.foo.org)
Sep 4 11:40:46 bigboss named[17881]: /etc/bind/db.local:41: ignoring
out-of-zone data (atos.local.foo.org)
...
The zone is correctly saved after the named shutdown. Here's and extract
of the zone.
$ORIGIN .
$TTL 60400 ; 16 hours 46 minutes 40 seconds
local.foo.org IN SOA bigboss.local.foo.org. root.local.foo.org. (
2007104311 ; serial
604800 ; refresh (1 week)
86400 ; retry (1 day)
2419200 ; expire (4 weeks)
604800 ; minimum (1 week)
)
NS bigboss.local.foo.org.
NS leporetto.local.foo.org.
NS zerlinda.local.foo.org.
A 192.168.0.1
MX 10 bigboss.local.foo.org.
$ORIGIN _tcp.local.foo.org.
_jabber SRV 5 0 5269 jabber.local.foo.org.
_xmpp\226\136\146client SRV 5 0 5222 jabber.local.foo.org.
$ORIGIN local.foo.org.
_xmpp\226\136\146server SRV 5 0 5269 jabber
admbess A 192.168.0.68
aida A 192.168.0.121
$TTL 604800 ; 1 week
alvaro A 192.168.0.14
$TTL 43200 ; 12 hours
Amazone A 192.168.0.19
TXT "31020f5f78b8ffc7c40756e688ff0df565"
$TTL 60400 ; 16 hours 46 minutes 40 seconds
aramis A 192.168.0.108
$TTL 604800 ; 1 week
arlequin A 192.168.0.32
$TTL 43200 ; 12 hours
Arpagon A 192.168.0.5
TXT "31be311b20c4c0589cbf72dc28f090a715"
$TTL 60400 ; 16 hours 46 minutes 40 seconds
atos A 192.168.0.113
$TTL 604800 ; 1 week
candide A 192.168.0.43
$TTL 43200 ; 12 hours
If I manualy remove the $TTL and put back @ SOA record, the named loads
the zone without any problem, else, the zone is not loaded.
Can anyone explain me, the mistake I made ?
S. Bernard
