Help with Named, DHCP-Update

Ed Warner edwarner99 at yahoo.com
Mon May 19 01:38:06 UTC 2008


Kirk <bind at kirkb.net> wrote: Ed Warner 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
> 
> 
> I think I have the Named problem fixed. I revamped my files as seen 
> below. They are simpler thanks to your comment. Do these look ok as far 
> as syntax goes?
> 
> named.mylan
> 
> $ORIGIN .
> $TTL 1D        ; 1 day
> mylan.lan.        IN     SOA    bonsai.mylan.lan. root.localhost. (
>                     200818742  ; serial
>                     28800      ; refresh (8 hours)
>                     14400      ; retry (4 hours)
>                     3600000    ; expire (5 weeks 6 days 16 hours)
>                     86400      ; minimum (1 day)
>                     )
> 
>             IN    NS    bonsai.mylan.lan.
> bonsai.mylan.lan    IN    A    192.168.100.1
> ----------------------------------------------------------------------------------------
> named.mylan-rev
> $TTL 1D        ; 1 day
> @            IN     SOA    bonsai.mylan.lan. root.localhost. (
>                     200817843  ; serial
>                     28800      ; refresh (8 hours)
>                     7200       ; retry (2 hours)
>                     604800     ; expire (1 week)
>                     86400      ; minimum (1 day)
>                     )
> 
>             IN    NS    bonsai.mylan.lan.
> 10            IN    PTR    bonsai.mylan.lan.
> 
> 1            IN    PTR    localhost.
> --------------------------------------------------------------------------------------------
> 
> Any ideas on the DHCP?
> Thanks again for your help.
> 
> Ed
> 

Well, sorta.

In the mylan.lan zone file you have:

bonsai.mylan.lan    IN    A    192.168.100.1

BIND interprets this as:
bonsai.mylan.lan.mylan.lan.    IN    A    192.168.100.1

because you didn't terminate the name with a "."




In the reverse zone you have:

10            IN    PTR    bonsai.mylan.lan.

shouldn't this be:
1            IN    PTR    bonsai.mylan.lan.

to match the "A" record above in the mylan.lan zone file?
My bad. Ignorance on my part not placing the "." 

You are right, it should be:
 1            IN    PTR    bonsai.mylan.lan.

When I restart named, something makes the change. I don't understand.

       



More information about the bind-users mailing list