Virtualmin duplicating hostname A records (possible bug)

What in the docs.
its how it is in the docs

Its a pretty standard method, check google.

No… the server templates page and the post-install walkthrough page where both use the word ā€˜hostname’ - will people think that is supposed to be the server hostname/FQDN? (Like I did)

Maybe Primary DNS server hostname should instead say Primary DNS Nameserver?

Yeah, I just use server.domain.com but i don’t use that name for the DNS addresses.

Its explained in docs

I’ve always use external dns so its never been a name that I’ve used for dns. Like the docs says if you want it as a primary DNS then better name might be ns1.domain.com

Virtualmin does not want anything. It is but a humble servant.

There are things I think people should do on their hosting systems, but this is not an area I have any opinions on. Name your name servers anything you want. There is no standard and no rule. Many people choose to use ns1, ns2, etc. for the name of their name servers. Virtualmin will choose the system hostname as the first name server if you don’t tell it otherwise, just because it knows that’s getting setup as a name server with all the appropriate records for the sites it’s managing. But, that is not a ā€œwantā€, or a recommendation or anything else. You NS records do not have to have anything to do with the system hostname, but it doesn’t hurt anything if they do. (Just don’t name your server the same as a name you’ll be hosting in Virtualmin.)

I’d have to admit that the only reason I started using hostname.domain.tld as the Primary DNS server hostname is because virtualmin has the word hostname in that label.

Would there be any difference in using Primary DNS server hostname vs Primary DNS Nameserver as that label? If not I reckon using the latter might help avoid confusion and maybe not pre-populate that field in the post-install wizard (I’m guessing I can’t be the only one who thought that virtualmin might need the hostname to be one of the NS servers since it’s in the label and because it pre-populates that field).

We should probably split this thread as we’re now discussing two things (the duplication of A records and the hostname/wording).

They’re all ā€œhostnamesā€. Every A record is a hostname. What you name your server is a hostname, but it’s not ā€œthe hostnameā€. Every other A record for that IP is also a hostname for that server.

But, yes, we’re off-topic. I guess we can try to rework the language of that page, if ā€œhostnameā€ is confusing. Maybe just needs a bit more explanation of what it’s doing and that it’s not recommending anything, it’s just trying to make things work for folks who may not know a lot of about DNS.

Coming back to the original issue of why there are two A records, I found the cause of this bug and will include a fix in the next release.