Help with Named, DHCP
Ed Warner
edwarner99 at yahoo.com
Mon May 19 02:00:29 UTC 2008
Kirk <bind at kirkb.net> wrote: Ed Warner wrote:
> Kirk wrote:
>> These are the errors I am getting when I start named. Named.conf is below.
>>
>> May 16 13:05:42 bonsai named[16871]: starting BIND 9.5.0b2 -u named -t /var/named/chroot
>> May 16 13:05:42 bonsai named[16871]: found 1 CPU, using 1 worker thread
>> May 16 13:05:42 bonsai named[16871]: loading configuration from '/etc/named.conf'
>> May 16 13:05:42 bonsai named[16871]: listening on IPv4 interface lo, 127.0.0.1#53
>> May 16 13:05:42 bonsai named[16871]: listening on IPv4 interface eth1, 192.168.100.1#53
>> May 16 13:05:42 bonsai named[16871]: default max-cache-size (33554432) applies
>> May 16 13:05:42 bonsai named[16871]: default max-cache-size (33554432) applies: view _bind
>> May 16 13:05:42 bonsai named[16871]: command channel listening on 127.0.0.1#953
>> May 16 13:05:42 bonsai named[16871]: zone 0.0.127.in-addr.arpa/IN: loaded serial 2007022700
>> May 16 13:05:42 bonsai named[16871]: zone 100.168.192.in-addr.arpa/IN: NS 'bonsai.mylan.lan.100.168.192.in-addr.arpa' has no address records (A or AAAA)
> misconfiguration in the 100.168.192.in-addr.arpa zone file(notice how
> *bonsai.mylan.lan* & *100.168.192.in-addr.arpa* run together in the error
> above) and your NS record *bonsai.mylan.lan* does not have an associated A
> record.
>
>> May 16 13:05:42 bonsai named[16871]: zone 100.168.192.in-addr.arpa/IN: loaded serial 200717841
>> May 16 13:05:42 bonsai named[16871]: zone mylan.lan/IN: NS 'bonsai.mylan.lan' has no address records (A or AAAA)
>
> Your NS record does not have an associated A record.
>
>> May 16 13:05:42 bonsai named[16871]: zone mylan.lan/IN: loaded serial 200718740
>> May 16 13:05:42 bonsai named[16871]: zone localhost/IN: loaded serial 42
>> May 16 13:05:42 bonsai named[16871]: running
>> --------------------------------------------------------------------------------------------
>
>
>> ===========================================================
>> named.mylan
>> $ORIGIN .
>> $TTL 86400 ; 1 day
>> mylan.lan IN SOA bonsai.mylan.lan. root.localhost. (
>> 200718740 ; serial
>> 28800 ; refresh (8 hours)
>> 14400 ; retry (4 hours)
>> 3600000 ; expire (5 weeks 6 days 16 hours)
>> 86400 ; minimum (1 day)
>> )
>> NS bonsai.mylan.lan.
>> $ORIGIN mylan.lan.
>> 1 A 127.0.0.1
>> 2 A 192.168.100.1
>> $TTL 302400 ; 3 days 12 hours
>> Azalea A 192.168.100.5
>> TXT "3109b3d6e9ef1a0f01e89f135933477030"
>> pine A 192.168.100.49
>> TXT "31cc68c5aeef56368c390717062cd52286"
>
> Your NS record does not have an associated A record causing the errors when
> you start named.
>
> As I am learning here, could you help me with what needs to be added or changed and why?
> Thanks,
>
> Ed
>
>
>
To assist in learning I suggest *not* using the zone file syntax *shortcuts*.
This will enable you to see what BIND sees. Based on the zone information
you have above, below is your zone file as BIND see's it(without the
shortcuts).
mylan.lan. 86400 IN SOA bonsai.mylan.lan. root.localhost. (
200718740
28800
14400
3600000
86400 )
mylan.lan. 86400 IN NS bonsai.mylan.lan.
1.mylan.lan. 86400 IN A 127.0.0.1
2.mylan.lan. 86400 IN A 192.168.100.1
Azalea.mylan.lan. 302400 IN A 192.168.100.5
Azalea.mylan.lan. 302400 IN TXT "3109b3d6e9ef1a0f01e89f135933477030"
pine.mylan.lan. 302400 IN A 192.168.100.49
pine.mylan.lan. 302400 IN TXT "31cc68c5aeef56368c390717062cd52286"
Is this what you are expecting? Notice that "bonsai.mylan.lan." does not
have an "A" record. If a hostname doesn't have and "A" record then it cannot
be resolved to its IP address. Since it's name cannot be resolved, BIND is
warning you about this in the log file.
This looks like what I am expecting. The "Azalea" and "pine" entries are inserted by ddns. With what you "translated" for me, I am not clear how to insert the A record for bonsai.mylan.lan
More information about the bind-users
mailing list