These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for DNS Zone Error on the new forum.
When I check the Virtualmin config it gives me the following error:
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.So I added 127.0.0.1 to the list. I then applied the configuration. I checked again and it gave me the same error. I took a look at the list again and found that all the changes that I made a minute or two before had been erased. I tried again with the same result.
I tried to edit resolv.conf manually, but the same exact thing happened.
Any help is greatly appreciated! :)
uname -a:
Linux 2.6.28-11-server #42-Ubuntu SMP Fri Apr 17 02:48:10 UTC 2009 i686 GNU/LinuxI'm running Ubuntu 9.04 (server edition) with the ext4 filesystem.
That sort of thing can happen if another program is changing your resolv.conf file back to what it was -- such as DHCP.
You need to prevent DHCP from overwriting your resolv.conf, or move to a statically configured IP address.
-Eric
Thanks! I'll try that out. :)
I solved the problem by uncommenting the following line in /etc/dhcp3/dhclient.conf
#prepend domain-name-servers 127.0.0.1;
Thanks for your help! :D
Sorry for posting again but I kept getting a bug error when I tried to edit the post.
The line I uncommented is:
#prepend domain-name-servers 127.0.0.1;
Thanks again!
Yeah the forum is terrible -- it'll be replaced soon :-)
Glad to hear your got your DNS issue working though. Have a good one!
-Eric
I had the same problem and solved it by reading this topic. thank you
I'm having the same problem. Which file in CENTOS 5.3 do I need to edit ?
Howdy,
The file for the content he mentioned above is "/etc/dhcp3/dhclient.conf ". -Eric
Eric,
Can't find /etc/dhcp3/dhclient.conf on centos 5.3. Any idea why?
He's using Ubuntu, so you might have a different version of dhclient.
Look for another dhclient.conf in /etc/, I don't recall where it is in CentOS. -Eric
If you are in Centos 5.6, it is in /etc/dhcpd.conf
Using Virtualmin may be in /etc/dhclient-eth0.conf (...or whichever port you are using, eth1, etc.)
If using Cloudmin KVM, create a file named /etc/dhclient-br0.conf and add it in there.
you should add the 127 IP through webmins networking module, save it but do not click the apply configuration button as then it will be gone.
Go to Webmin-->Networking-->Hostname and DNS Client--> then
in DNS servers Add: 127.0.0.1
Save, and re-check the system.
Dear friends,
I installed last version of webmin and virtualmin:
Operating system CentOS Linux 6.2 Webmin version 1.580 Kernel and CPU Linux 2.6.32-71.el6.x86_64 on x86_64
There wasn't any dhclient.conf file even when I installed dhcp .(I created it with a line that mentioned, but was not solved) also in Webmin > networking there isn't Hostname and DNS Client option. What should I do? Please help me
The problem is : 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.
when I click on "Re-check and refresh configuration" button .
Howdy,
The option you're looking for is in Webmin -> Networking -> Network Configuration -> Hostname and DNS client.
There's some more details here:
http://www.virtualmin.com/documentation/dns/faq
I made all the changes but still the same problem..when i hit aply config in network config...the same error ..to add 127.0.0.1 in dns
Pls help
read more post and i figured it out. Edit /etc/dhcp/dhclient.conf coment out prepend domain-name-servers 127.0.0.1; Edit in Virtualmin/ System Settings/Virtualmin Configuration/Advence Options/ and make Check resolv.conf for this system? to NO Apply all changes. Restart Network Interfaces Re-check config Done Sorry for my English :)
Just to let Everyone know, Excellent observations. Works perfectly on my installation and fixed the error with DNS.
Thanks