I am getting this error everytime I log into virtualmin. I enter 127.0.0.1 and if I log out and log back in, I get the same error. Anyone know why this is?
Here’s the error:
The status of your system is being checked to ensure that all enabled features are available, that the mail server is properly configured, and that quotas are active …
Virtualmin is configured to setup DNS zones, but this system is not setup to use itself
as a DNS server. Either add 127.0.0.1 to the list of DNS servers,
or turn off the BIND feature on the module config page.
… your system is not ready for use by Virtualmin.
When you say “logged out and back in”, do you mean log out of Virtualmin?
In that case, it sounds like what you’re adding there isn’t being saved.
Just to be sure – if you go into Webmin -> Networking -> Network Configuration -> Hostname and DNS Client, add “127.0.0.1” to “DNS servers”, then hit “Save” at the bottom – does that work? Or do you have the same problem?
I have sometimes seen it where if your system is using DHCP, anytime it obtains a new IP address, it can also overwrite your current nameservers with whatever the DHCP server is providing. Which would cause the problem you’re seeing.
Thanks for the reply. I have saved it where you’re stating. And yes, it does do it just by logging out and logging back in. My IP hasn’t changed at all. However, I am set-up on DHCP. Any other suggestions?
Hrm, after you make those changes – take a look in /etc/resolv.conf, what are the contents of that file?
You can do that by typing:
from the command line.
Appreciate the help, but I guess I’m gonna have to do a re-install of Centos and Virtualmin. My server keeps hanging up. Maybe something was wrong with the installation. Once installed, I’ll post here if I’m having the same problems. Thanks!
switching from dhcp to a static IP doesn’t recquire a full reinstall though.
old thread but I have the same issue after installing on CentOS 7… When I go into the module and add 127.0.0.1 to the name server list it’s fine after hitting save. As soon as I reboot the system it’s gone and the error is back.
After adding it I checked the resolv.conf through SSH and it’s there… after reboot… gone.
Any advice on this bug??
I may just go into the virtualmin config settings and turn off the resolv.conf check under advance settings. The server runs fine and serves pages even when this error shows up on system check…
I did notice when this happened in the past changing the theme to the authenic one saved the changes to DNS list and it stuck… is this a theme issue??
Hmm, it doesn’t sound like you’re seeing a bug… that behavior would occur if the interface was setup to use DHCP.
It can also occur with some VPS’s.
Can you verify that your particular interface setup as static?
100% verified. Yes all static. Bug.
Well, it doesn’t sound like a bug – something is changing your /etc/resolv.conf file.
The key is to figure out what.
Is this a VPS, or a dedicated server? If it’s a VPS, what kind of VPS is it?
Adding 127.0.0.1 only seems to work with Debian, Ubuntu does not accept or save the input, you have to change from DHCP in /etc/network/interfaces.
With Ubuntu I change it so something like this…
The primary network interface
iface eth0 inet static
dns-nameservers 127.0.0.1 **.***.16.6 **.***.16.7
post-up iptables-restore < /etc/iptables.up.rules
Or it can be em1, depends on your provider etc.
Never had to do it before with Ubuntu but things seems to have changed, I don’t think it’s a VM isuue but provider or buntu. Not a network expert here.
In addition to whether you’re using a VPS or dedicated server, which distro/version is it that you’re seeing there?