Hmm, sorry for creating another thread, but thought this deserves its own thread. This question was asked few times in this forum, but i was unable to find a clear answer that i would follow. So it would be awesome if someone can give me a quick fix for this (would help everyone else too)…
Any way, i was trying to run “Re-Check Config” under “System Settings” and i get the following:
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.
any idea how to Fix this?
Im running CentOS 5.5 on a VPS hosted by volume drive (if that helps).
Just to add, im really noob, so it would be greatly appreciated if you can explain a tiny bit in detail what i can/should do…
i can simply add 127.0.0.1 to the list of DNS servers (this fixes the problem)… but sadly, when ever i restart my vps, the list of dns servers resets back to default and i get this same error again… so i guess every time i restart my server i can remember to add this again, but is there any way to fix this (or prevent this from happening)? O.o
Chances are that’s happening due to your IP address being obtained by DHCP. By default, the DHCP client will set a number of things, including the DNS servers.
To prevent that, edit /etc/dhclient-eth0.conf , and make sure there is a line like :
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.
I add 127.0.0.1 and then when you restart, the same thing again.
haha yeah, i never found a solution to this… have to manually set the 127.0.0.1 every time i restart… siigh, its annoying… Any idea what will happen if i ever forget this?
and thanks Locutus, will have a look at that link later, see if it helps me at all…
I see this is an old thread, but maybe someone else searching could make some use from it.
To fix the issue relating to 127.0.0.1 not staying after a reboot or when ever.
I did this on a desktop version of ubuntu.
open the network connections icon, then highlight your network interface. now click edit to that interface.
I am assuming the IP has been setup static and you are behind a router.
Look at the DNS section, and add 127.0.0.1
You may need to find out what your DNS ip’s are. (You can do this be looking in your router.)
here is an example of how mine DNS setting look in my settings.
I wonder, does it even matter if 127.0.0.1 is not listed. Doesn’t it just mean that lookups will be done remotely instead of locally?
If someone knows what is the counterpart for the shell (I doubt if much people use a desktop on their server) for the desktop solution on CentOS 6 or Scientific Linux 6 then please let us know.
I can’t believe that this is still happening on my CentOS 6.5. And no, my IPs are not assigned by DHCP. I tried manually entering the IP 127.0.0.1 into /etc/resolv.conf but it only stays there until server reboots.
The OpenVZ container (running CentOS 6/64 bit) is up and running with lo/venet0/venet0:0 interfaces and a public IP - but there are no entries under /etc/sysconfig/networking/devices/
Note that the OpenVZ container was set up by and is running via Proxmox.
And it’s not a real issue here, I just added the 127.0.0.1 entry and everything works nicely.