The BIND DNS Server configuration on your system has errors

Help! (Home for newbies)
1
SYSTEM INFORMATION
OS type and version Ubuntu Linux 24.04.4
Webmin version 2.630
Virtualmin version 8.1.0 GPL
Webserver version nginx
Related packages BIND

I got this error on dashboard:

The BIND DNS Server configuration on your system has errors! This will prevent any new domains from being fully added by Virtualmin until the errors are fixed.

zone mydomain.id/IN: NS 'sumo.mydomain.id' has no address records (A or AAAA)
zone mydomain.id/IN: not loaded due to errors.
_default/mydomain.id/IN: bad zone

my system hostname is sumo.mydomain.id and i have a virtual server at sumo.mydomain.id as reverse proxy to access virtualmin dashboard with SSL.
I also have alias virtual server for mydomain.id that shows my2nddomain.id. It is where my website file is.

this is my /var/lib/bind/sumo.mydomain.id.hosts content:
domain and IP are redacted.

$ttl 3600
sumo.mydomain.id.	IN	SOA	sumo.mydomain.id. root.sumo.mydomain.id. (
			2026012613
			3600
			600
			1209600
			3600 )
@	IN	NS	sumo.mydomain.id.
sumo.mydomain.id.	IN	A	123.123.123.123
www.sumo.mydomain.id.	IN	A	123.123.123.123
webmail.sumo.mydomain.id.	IN	A	123.123.123.123
admin.sumo.mydomain.id.	IN	A	123.123.123.123
sumo.mydomain.id.	IN	TXT	"v=spf1 a mx a:sumo.mydomain.id ip4:10.11.13.14 ip4:123.123.123.123 ?all"
@	IN	CAA	0 issue letsencrypt.org

Can anyone help me to pinpoint my issue?

2

hostname shouldn’t be the same as domain your going to host.
Not sure that is the cause of your NS record issue but avoid it.
Use something like server.mydomain.id

image
image1200Ă—218 19.6 KB

3

While that’s true, it’s probably not relevant here.

That piece of advice is about mail delivery and the fact that Virtualmin sets up virtual users for domains managed by Virtualmin, which conflicts with local users if you name both a virtual domain and the system the same thing. It remains a suboptimal idea, but if you’re not receiving mail for that name on the server (and mail is disabled in the Virtual Server), you are probably fine.

That advice rarely has anything to do with DNS, though it’s easy to mess up DNS if you have zones for both domain.tld and sub.domain.tld managed by Virtualmin…it usually gets it right, but the NS thing hints that maybe the NS record got set to the hostname for all zones, and now there’s some kind of circular thing happening here, I’m not sure. So maybe it’s kind of indirectly related to the decision to name the system the same thing as a domain hosted in Virtualmin.

Without the actual hostnames and IP, I probably can’t really help troubleshoot, as I can’t dig around to see what’s actually being served and who’s authoritative for what.