However, the default primary DNS server does not resolve to an IP address

Virtualmin
1
SYSTEM INFORMATION
OS type and version Ubuntu 24.04 LTS
Webmin version 2.402
Virtualmin version 7.30.8
Webserver version 1.24.0
Bind version 9.18.30

I just made a new reinstallation of Virtualmin on a brand-new server. The install went well but I noticed this strange sentence after running the final configuration check:

BIND DNS server is installed, however, the default primary DNS server NN does not resolve to an IP address

I feel like this may bring problems to my zone verification if I use the FQDN in it. Is there a way to solve this and couldn’t that be done automatically?

2

Have you seen this?

1 Like
3

I didn’t see it but now I have read it. However, this is not a documentation related with the problem I list above. This page is about correctly setting up the zone of a domain I want to serve from my Virtualmin server.

My question is about Why virtualmin does not see that the FQDN I choose for him resolves to an IP address.

The domain name I chose is set up correctly on another server and points to the VPS where I have Virtualmin.

NN. A xxx.xxx.xxx.xxx
NN. AAAA yyyy:yyyy::yyyy

When I check how it resolves from the server itself I see:

dig NN

NN.		0	IN	CNAME	ubuntu-24.localhost.
NN.		0	IN	A	xxx.xxx.xxx.xxx

;; ADDITIONAL SECTION:
ubuntu-24.localhost.	0	IN	A	127.0.1.1

I think that because of the CNAME, I have this remark post installation:

BIND DNS server is installed, however, the default primary DNS server NN does not resolve to an IP address

As a result, when I want to use this name as a primary name server in a zone I get the following message:

Screenshot de virtualmin

This is quite anoying.

4

I can’t tell what I’m looking at, as that doesn’t seem valid. I guess you’ve changed the IPs to words here to anonymize them? I can’t really tell you what’s wrong without seeing what’s actually happening.

5

Is it the same IP address as before? If not, you need to change the glue record at the registrar.

A and AAAA records are IP addresses, not names. As @Joe asked, did you change this just for the forum posting? Why not just uses X’s in the proper format for clarification? xxx.xxx.xxx.xxx

6

Sorry, this is confusing indeed. Let me change this into xxx.xxx.xxx.xxx to make it clearer

1 Like
7

Does mxtools resolve the FQDN ?

image
image975×518 19.7 KB

The FQDN should also be a name NOT used by any virtual servers as stated in the docs.

image
image1215×364 49.5 KB

I’ve done a ton of installs of virtualmin and never run into this problem but I’ve always used a external dns pointing to the ip before install.

8

Well no, new VPS means a brand new IP and a brand new FQDN

I didn’t change anything at a registrar as the FQDN is not a first level domain, but I created a new entry in the zone I manage. Oh and yes I updated the PTR an the hoster.

I don’t know mxtool but dig @9.9.9.9 or anywhere else resolves it.

Good reminder, but this is not the case here.

9

Maybe you didn’t notice the sentence after setup. Do you use the FQDN as a primary NS name ?

10

Nope, I have external name servers.

11

I gave up on trying to have ‘tidy’ DNS records and just write the stuff out in full. Well, now WM/VM does that for me.

Try dropping the cname and just using the full nn.domainname.tld for the a and aaaa records and see what happens.

12

Except that this zone is configured by Virtualmin at installation time and VM doesn’t give me access to it. Only to the zones for virtual servers.

I guess I could find it via ssh but I would prefer like to figure out what it is here for. Just before I break things…

13

Have you looked at the server index under Webmin? I think ALL DNS zones should show there.

14

The zonefile of the FQDN appears here, however, the CNAME with ubuntu-24.localhost. is not in this zonefile.

15

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.