While checking the logs of my server, I ran into the following errors:
May 11 18:00:04 named[31875]: zone example.com/IN: NS 'ns1.example.com' has no address records (A or AAAA)
May 11 18:00:04 named[31875]: zone example.com/IN: NS 'ns2.example.com' has no address records (A or AAAA)
May 11 18:00:04 named[31875]: zone example.com/IN: NS 'ns3.example.com' has no address records (A or AAAA)
I ran into the same errors when I checked the zone files themselves using:
named-checkzone example.com /etc/bind/zones/example.com
. So it appeared to be a syntax error. However, with other zone files on the server validating fine, it seemed that the issue was particular to the example.com zone file alone.
Comparing the problematic zone file against a healthy one highlighted the discrepancy. The domains of the nameservers in the example.com zone files were not terminated with a period (unlike the rest of the domain names in the file). Once this was fixed, all was peachy once again. The zone file validated successfully and my logs are bereft of these errors!
I hope this helps somebody out there :)
- Log in to post comments
Comments
Did you already have a solution?
I would suggest to get a default file from www.zonefile.org. And than simply copy an paste. ;) Did you have a named.conf entry?
Thanks for the message and
Thanks for the message and the link - that looks handy!
As for my problem, I was missing a period (as stated in my post).
Cheers :)
Yeah, it helped. Thanks
Yeah, it helped. Thanks
Useful
It helped me! Thank you!
Mihai
Same error, different reason,
Same error, different reason, in my case. You had a mangled A record, but I simply had none at all. When I ran "named-checkconf /etc/bind/named.conf" it showed no problems with the configuration. It was only when I used "-z" to do a trial load of the zone files ("named-checkconf -z /etc/bind/named.conf") that I got your error. The moment I added an A record, things started working much better :-) This was all with Webmin 1.610 on Ubuntu 10.04. Thanks.