Not sure if this is relevant but this seems like a strange result. I’m guessing maybe this is only because the name servers are set up for internal use only? I get a different answer if I don’t specify the name server.
mit@~:dig @46.38.225.230 v220241254536303498.supersrv.de
; <<>> DiG 9.18.28-1~deb12u2-Debian <<>> @46.38.225.230 v220241254536303498.supersrv.de
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 12060
;; flags: qr rd ad; QUERY: 0, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; Query time: 135 msec
;; SERVER: 46.38.225.230#53(46.38.225.230) (UDP)
;; WHEN: Wed Dec 25 10:27:26 EST 2024
;; MSG SIZE rcvd: 12
Can you ping the address from the server to see if it resolves?
Just as an aside, I would recommend folks be careful fiddling with the Network Configuration pages in Webmin on a virtual machine at a hosting provider. There are no user serviceable parts in the network configuration on a virtual machine; leave it alone. If you change anything related to IP, routing, DHCP, etc. you can only break connectivity to the server, you can’t make anything better.
The only thing you can safely change is the hostname, but it’s easy to break other stuff when messing around in Webmin’s Network Configuration pages.
I don’t know how the error can be more clear. That name (the hostname of the system) does not resolve to an IP address. The message has already answered the question of why it is showing the message.
You can avoid the error about resolving by simply telling it not to check. But, if you’re expecting a domain for the system hostname (for getting a Let’s Encrypt certificate), the name has to resolve.
We can’t make it resolve at this stage, only you (or your hosting provider) can make it resolve at this stage. Virtualmin is not managing anything that could make it resolve this early in the process. Either the hostname resolves, and it’ll get a cert and such, or it doesn’t and it won’t even try (and you can ignore the browser warning until you get some Virtual Servers setup in Virtualmin).
The system hostname virtual server that is automatically created during installation is a minor convenience feature to avoid a browser error the first time you login. It is not a thing you need to freak out about (though you probably do want your system name and IP to resolve, both forward and backward, if you’ll be sending mail directly from this system).
Normally the hostname provided by your host will resolve, so it’s kind of cruddy that it doesn’t in this case. But, you can rename your system to something in a domain you control, and create an A record so it does resolve. If you need the system hostname virtual server to be created, you’ll need to do that before you install Virtualmin. (But, you don’t need that virtual server for anything once you have regular Virtual Servers with TLS certs, you can just login using any of those names, instead).
