All sites have stop resolving!

7 posts / 0 new
Last post
#1 Mon, 04/15/2019 - 15:14

All sites have stop resolving!

Hi Everyone, I finally got my server up and running with Ubuntu 18.04 and Virtualmin. Everything was working fine for about two to three days. Then this morning nothing none of the sites resolve anymore? Checked all the dns settings and everything seems to be fine nothing has changed!

Does anyone have any ideas of what could have stopped the resolution suddenly like that?



Mon, 04/15/2019 - 20:47


Hmm, is BIND running?

If BIND has stopped for some reason, and your server is the nameserver for your domains, that could cause similar issues.

If your server is the nameserver, you may also want to ensure that is listed in /etc/resolv.conf.


Tue, 04/16/2019 - 03:26

Is system rebooted in that time? ( or network restarted)

While the resolv.conf with some hosters are replaced then for default ones, i am just testing here and having this on openstack instance.

If so make it right and lock with chattr +i resolv.conf

to unlock chattr -i resolv.conf

Tue, 04/16/2019 - 09:44
tzohosting Pro Licensee

I have reported a similar issue a month ago using AWS EC2 in a VPC, I have yet to get it resolved. I am beginning to think the Virtualmin may not be the best option with Ubuntu 18.04 (official AWS AMI) if on AWS EC2.

My guess is your server rebooted and lost all the internal IPs and has defaulted to a single IP. This has happened on multiple instances on fresh installs of Virtualmin. Never had this issue on Ubuntu 14 or 16. See issue here...

if anyone else has anything thoughts, I am all ears.

Tue, 04/16/2019 - 09:58 (Reply to #4)

Sorry your link has no access

Access Denied You are not authorized to access this page.

Are there things like cloudinit on those?

and differences ubuntu

Netplan is the replacement of ifupdown in Ubuntu. It is a new way to configure your network. However we found that it is incompatible with dhcpv6. This would make ipv6 non functional on this image when dhcp ipv6

also eno/ens network names. and not eth...

Tue, 04/16/2019 - 10:02 (Reply to #5)
tzohosting Pro Licensee

Sorry, I have a paid license and may only be for paying customers? In any case, yes on cloudinit. Here is the gist of the issue I reported.

"The specific issue is around creating virtual servers and assigning private IPs. Once you reboot, all of the IPs get lost and Virtualmin complains that the server IP has changed.

I have done a fresh install of Ubuntu 18.04.2 (Official AWS Provided AMI) and Set a FQDN hostname and installed latest Virtualmin under VPC. Install of Virtualmin was error free.

I can create virtual servers fine and give them private IPs and assign public IPs via AWS console. This works and serves sites fine. The network interface in Webmin > Networking > Network Configuration > Network and the interface all look correct.

However, when a reboot occurs, the network interface loses all the IPs for the virtual servers and defaults to the incorrect IP. It actually changes and defaults to the highest IP. Example, the server IP is, all virtual servers will have their own private IP as,, etc... But once a reboot happens, all virtual server IPs are lost and defaults to

I have no issue with this on Ubuntu 16.04.

My questions is, is this still a known issue? Is there a configuration change that must take place to work with multiple IPs?"

Tue, 04/16/2019 - 10:10

You see some important diferences so it could be working if you change / revert the not working parts to as it was in old version. I have edited my post above

Also some networking parts are replaced / overwriten at reboots as often resolv.conf .... cloudinit for cloud / openstack and so on.

Example of a openstack where >

I'm testing also private ips AND CENTOS ( so no experience with UBUNTU ! IPV4 working ipv6 for the moment can't get it running for outside access, tough the ipv6 external is on the instance as i can see in network for eth1