I wonder if this is a side-effect of the new code that copies a TLS cert to BIND? It does touch those listen-on directives, but only adds new ones for port 853.
For anyone who is seeing this - what listen-on lines were in your named.conf file before Virtualmin was installed?
Yes, on Debian and Ubuntu, the stock BIND config only sets listen-on-v6 { any; }, and IPv4 listening on port 53 comes from BIND’s built-in default.
Once we add any listen-on directive for IPv4 that implicit default is replaced.
That said, on Debian and Ubuntu we should also add listen-on port 53 { any; }; to /etc/bind/named.conf.options config file to keep the original behavior.
Ok this should be fixed here : Add the default BIND listen-on for port 53 if there were none to star… · virtualmin/virtualmin-gpl@7b9912a · GitHub
Confirmed, it does fix it! Thanks!
For 3 days I was not able to do anything else. I have one issue with one server after Update. I did full re-install but the base domain could not resolve. I even got a New Server, still not Resolved. Change Provider Still nothing.
I came here and found this Post, I hope to get full guide: File and directory to modify.
I am Using Ubuntu. 22.04 after downgrade.
Thank You!
You can apply the patch like this:
webmin patch https://github.com/virtualmin/virtualmin-gpl/commit/7b9912a
And, just make sure that BIND listens on port 53. That’s it.
I was now busy with my last try before I give up and was noting all the steps and error to start a new topic afterword.
I have been using VM for over 10 years now and never and any issue, only related to individual Virtual Servers.
Please How to I apply the patch? File and directory to edit please. It’s 5 been days now I have not done any thing else. I have done over 200 attempts. Ans the issue i Am facing now is exactly with Bind Config.
Thank You.
Hi friend. A workaround that solved this for me on a fresh installation was to avoid using the VPS’s fully qualified hostname during setup. If you start with a simple hostname (like server-25 instead of server.example.com), the installer will detect that it isn’t fully qualified and prompt you to enter one manually.
When I typed in the correct FQDN at that prompt, all the DNS issues disappeared for me. It seems the installer handles the hostname configuration correctly only when the FQDN is entered manually, rather than when it tries to auto-detect one from the VPS provider.
I Finally Gave up. Something to do with the new Update. I will wait until there is a stable Update.
I Ended up using something and it works even better for me.
There is no need to wait, and the solution is primitive: