Hi all, On a single domain among many the A record for www doesn't work at all. I deleted and added again the record (usually resolves straight away) again, restarted bind and no luck. It always says server can't find the www.mydomain.com while mydomain.com resolves fine. This is very bizarre, never seen it before. Any ideas how to troubleshoot this? This is on a multi server setup with master/slave servers dedicated for DNS.
Use a DNS tester like intodns.com to verify the zone settings. Check the generated BIND zone file on all servers if it contains the A-record.
intodns shows same as when I do a nslookup (WWW A Record ERROR: I could not get any A records for www.mydomain.com). Where are stored the bind zone files as under /etc/bind/ there are many files. Is it the one that ends up .signed?
Under .signed it is the A record for www. Below I paste the whole file (I've just replaced the domains and IPs) $TTL 3600 @ IN SOA dns1.mycompany.com. admin.mycompany.com. ( 2023042007 ; serial, todays date + todays serial # 7200 ; refresh, seconds 540 ; retry, seconds 604800 ; expire, seconds 3600 ) ; minimum, seconds ; mydomain.com. 3600 A 1.1.1.1 www 3600 A 1.1.1.1 mydomain.com. 3600 AAAA 1.1.1.1 www 3600 AAAA 1.1.1.1 mydomain.com. 3600 DNAME smtpsign._domainkey.mydomain.com mydomain.com. 3600 CAA 0 issue "letsencrypt.org" mydomain.com. 3600 MX 10 email1.mycompany.com. mydomain.com. 3600 NS dns1.mycompany.com. mydomain.com. 3600 NS dns2.mycompany.com. mydomain.com. 3600 TXT "v=spf1 mx a ~all" $INCLUDE /etc/bind/Kmydomain.com.+007+00362.key $INCLUDE /etc/bind/Kmydomain.com.+007+40221.key
It's often most efficient to debug such errors with named-checkzone just run it like this: named-checkzone /etc/bind/mydomain.tld.zone mydomain.tld and it will tell you if the zonefile contains any errors and will not be loaded.