Big sudden problem: No server (A Record) behind your hostname

1

Hello:

My box uses DNS as suggested, managed in the same box, with DNSSEC and everything, following all the rules. Only mail accounts use external DNS. Version v0.26b.

It has been running flawlessly for 4 months.

After some delivery problems from yesterday, I have checked the box with www.mail-tester.com
getting a score of 4.2 (The usual score for all accounts/domains were 10)

The report says: We didn’t find a server (A Record) behind your hostname box.nbserver.net.

I have updated MAB to the last version, v0.26c. but nothing has changed.

Any suggestion will be greatly appreciated.

Jeremy

1 Like
2

I have the very same problem. It seems that my jungers.net domain use an expired DNSKEY. The system check of mail in the box fails.

the dns_update fron cron.daily fails with
All nameservers failed to answer the query back.jungers.net. IN A: Server 127.0.0.1 UDP port 53 answered SERVFAIL

Still stuck at this point.

Nicolas

3

I still don’t know what happened, but here what I have done to solve the problem.

I copied the zone from a slave server. I declared it as master in the local bind (in /etc/bind/named.conf.local) and the the update script (/root/mailinabox/tools/dns_update) that query that dns on the localhost:53 port was happy enough to do its job.

Then I removed the declaration of the master zone in /etc/bind/named.conf.local.

That’s it.

4

If MiaB uses nsd as the name server, I am wondering how adding the zone to bind had any effect. AFAIK, bind is not running.

5

On my MIAB, stock install, there is a bind name server restricted to localhost:53. nsd listen to the public addresses.