LinuxQuestions.org - Bind 9.7 Issue (NS ... has no address records)

- Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)

- - Bind 9.7 Issue (NS ... has no address records) (https://www.linuxquestions.org/questions/linux-networking-3/bind-9-7-issue-ns-has-no-address-records-851431/)

Bind 9.7 Issue (NS ... has no address records)

Hi,

I'm in the process of moving our primary nameserver from bind 9.2.4 on a Redhat 3 machine to bind 9.7.0 on a Redhat 6 machine. I've run into a problem and I haven't figured out how to address it yet.

I've changed our actual domain name to domain.com for this posting. The machine I'm working with is the master for domain.com, while we also have a subdomain called sub.domain.com which is which is handled by another group within our organization and which we slave.

Code:

$ORIGIN .

$TTL 7600

domain.com          IN SOA  ns1.domain.com. postmaster.domain.com. (

                                2004125168

                                3600

                                900

                                2592000

                                7600

                                )

                        NS      ns1.domain.com.                ; master

                        NS      ns2.domain.com.                ; slave, which we run

                        NS      ns1.sub.domain.com.        ; slave, run by the group which administers sub.domain.com

When I run named-checkzone, or when I try to start the server, I get the following error:

Code:

zone domain.com/IN: NS 'ns1.sub.domain.com' has no address records (A or AAAA)

Now this message makes sense since it's true that we do not, in fact, have any address records for ns1.sub.domain.com. Our current nameserver (bind 9.2.4), though, has never complained about this; and more importantly, I'm not sure how to properly address it.

In one sense, it seems obvious that I should simply add an address record for ns1.sub.domain.com; however, since another group handles sub.domain.com, and the nameserver ns1.sub.domain.com, should I really be messing with these records? Shouldn't I leave it to the group responsible for this? And if so, how do I tell bind this so that it knows sub.domain.com is handled by someone else and a record for ns1.sub.domain.com shouldn't be added locally?

Note that our named.conf file does have the following, defining sub.domain.com:

Code:

        zone "sub.domain.com" IN {

                file "slaves/named.sub.domain";

                type slave;

                masters { 1.2.3.4; };

        };

Any help would be appreciated.

Thanks.

I believe you will need to add an A record to match each NS record ...

Thanks kbp. How would this work if one of our slave servers was handled by an external provider for which we couldn't create an A record?

You create the A record in your domain.com zone -

e.g.

Code:

10.0.0.1 IN A ns1.sub.domain.com.

Hello! My first post! I'm a little late to the thread, but I didn't see an answer here and I ran into the same problem tonight moving our masters from a bind 9.3 system to a bind 9.7. Yes, we were still using 9.3 :).

We had to define the master servers for sub domains that wasn't required in earlier versions of bind. Once we defined the sub.doamin.com zone with an NS record in the domain.com zone, the zone loaded fine.

Try adding something like this in you zone file for domain.com:

sub.domain.com. IN NS "master server for sub.domain.com"

Forgot to mention the needed glu record. It worked for me without it since my master server was in my local hosts file.

"master server for sub.domain.com" IN A "IP of master server for sub.domain.com"

Hope this helps anybody looking for an answer like I was.