MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Originally posted by opjose If you haven't at least installed a caching nameserver, Mandrake will always add that line back in.
It's required so that X windows will run.
With a caching name server in place the machine knows it's own "name" by IP and the line is not required for localhost resolution.
Sorry but I don't think any of this is correct. X does not require a caching nameserver to function. 'localhost' can be resolved via the hosts file just fine.
There's absolutely NO reason this line needs to be in my resolv.conf file. Besides, the question isn't whether it's required or not, it's how does it keep getting added? What config file from Mandrake is adding this line back in? I've looked everywhere under /etc/sysconfig and can't seem to find it.
You misread my post. (lousy punctuation I used...)
X DOES require that the machine be able to determine it's own name.
When there is no entry for an active DNS nor eth0 hostname entry, it reestablishes the contents of /etc/resolv.conf at startup so that X knows which machine it is responsible for.
Yes, resolution via HOSTS also works, and you could do away with the /etc/resolv.conf file entry, but the scripts & programs will not see it and restore the localhost entries to /etc/resolv.conf to PROTECT the functionality of X.
This gets brought up every once in a while since others have encountered the same thing...
If it is not a mandrake specific thing, it is probably comming from your network script when it starts dhcpd. Try passing it the -R option to prevent this.
Originally posted by colnago If it is not a mandrake specific thing, it is probably comming from your network script when it starts dhcpd. Try passing it the -R option to prevent this.
No it's not a DHCP issue, it's a "Mandrake" thing.
It's specifically there for machines w/o ethernet interfaces to make X function properly.
Maybe this will help clear things up a bit. I have 1 interface, eth0, which has a static IP assigned to it. In my resolv.conf, in addition to the erroneous entry, I have my search domain listed correctly and my real nameserver listed correctly. If I leave the 127.0.0.1 entry in that file, it takes a long time to resolve anything (naturally, since it's not a DNS server). If I take that line out, resolution works very fast.
I am having the same problem only the address 192.168.8.1 keeps popping up and not only after reboot it pops up every 5 minutes or so. This address 192.168.8.1 is the address of my router and my router does use dns forwarding however this address does not work in linux only windows if I disable dns forwarding then my windows boxes stop working but the address keeps popping up in my resolv.conf. I am using mandrake. I was told to use the route command ok now how does the route command let me enter dns info. I checked the man pages and find nothing about dns so im lost there. I have also tried deleting the entry then typing chmod 100 which allows read to the owner and nothing else. This changes and permissions revert back to what they were before this also happens about every 5 minutes.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.