Since we are talking about DNS, it seems there is still one file giving trouble. Atleast to me. I tried installation on Ubuntu 22 and Debian 12. It was the same issue in both cases.
In /etc/bind/named.conf.options, there should have been these 2 lines -
listen-on port 53 { any; };
listen-on-v6 port 53 { any; };
Then, the entire section should look like this -
options {
directory “/var/cache/bind”;
// If there is a firewall between you and nameservers you want
// to talk to, you may need to fix the firewall to allow multiple
// ports to talk. See http://www.kb.cert.org/vuls/id/800113
// If your ISP provided one or more IP addresses for stable
// nameservers, you probably want to use them as forwarders.
// Uncomment the following block, and insert the addresses replacing
// the all-0's placeholder.
// forwarders {
// 0.0.0.0;
// };
//========================================================================
// If BIND logs error messages about the root key being expired,
// you will need to update your keys. See https://www.isc.org/bind-keys
//========================================================================
dnssec-validation auto;
listen-on port 53 { any; };
listen-on-v6 port 53 { any; };
listen-on-v6 { any; };
listen-on port 853 tls srv1048001_hstgr_cloud {
any;
};
listen-on-v6 port 853 tls srv1048001_hstgr_cloud {
any;
};
};
I spent several hours trying to figure out why my server was not reachable from the Internet. It was because by default there was no reference to port 53 in this file.
Hope this helps someone who still has issues with DNS and Nameservers after a fresh install.
There are other issues after a fresh install such as SSL but since this topic is not about errors after a fresh install, I am not posting those issues here. But I do hope the new version would address these issues.
I have replied to another OP here - Sites-enabled/anydomain.com.conf file error after Debian and Virtualmin and Webmin update - #2 by deepakdhingra