BIND9 fails with specific setup

Jezzirolk · 04-03-2010, 09:42 PM

when i try to set up bind9 to resolve the top level of the name it cant do it.
for current sake of arguement i have 4 servers on the network

192.168.0.200 diana.undernets.lan
192.168.0.201 jen.undernets.lan
192.168.0.202 amanda.undernets.lan
192.168.0.203 alex.undernets.lan

those are the IP addresses of the servers and their respective hostnames
so if i send a request for anything to just undernets.lan it will fail because there is no record for that. so i added this to the bottom of the zone record

Code:

               IN      CNAME   amanda

thinking that a blank would refer to the top of the zone

here is my named.conf.local which is called in my named.conf

Code:

zone "undernets.lan" {
        type master;
        file "/etc/bind/undernets.db";
};

zone "0.168.192.in-addr.arpa" {
        type master;
        file "/etc/bind/192.rev";
};

and here is undernets.db that works

Code:

@       IN      SOA     undernets.lan. root.undernets.lan. (
                            206         ;serial
                         604800         ;refresh
                          86400         ;retry
                        2419200         ;Expire
                         604800 )       ;TTL


        IN      NS      amanda.undernets.lan.

diana           IN      A       192.168.0.200
jen             IN      A       192.168.0.201
amanda          IN      A       192.168.0.202
alex            IN      A       192.168.0.203
;               IN      CNAME   amanda

if i remove the ; and make that not a comment then the whole server fails to resololve anything

is there a way to achieve what i am trying to do?
i want to be able to lookup undernets.lan and it give me the IP address of amanda.undernets.lan

bathory · 04-04-2010, 03:27 AM

Hi,

A blank space in the beginning of a Resource Record gets replaced by the $ORIGIN (in your case undernets.lan). So what you actually do is:

Quote:

undernets.lan IN CNAME amanda

that is not correct.
What you can do is:

Code:

   IN A 192.168.0.202

Regards

Jezzirolk · 04-04-2010, 09:05 AM

i tried what you suggested and put an entry in as

Code:

    IN A 192.168.0.202

and commented out the other entry with 192.168.0.202

but that fails to do anything i changed it in the zone file and in the reverse lookup file and restarted bind and still when i dig undernets.lan i get nothing in return. it says it has 0 answers. any ideas? my bind server is running on debian 5 if that is at all relevant

bathory · 04-04-2010, 09:22 AM

Have you increased the serial:

Quote:

206 ;serial

before restarting named?

You can also use, if you want, the whole zone name instead of a blank space:

Code:

undernets.lan.  IN A 192.168.0.202