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.
I had to reinstall my nvidia driver. I don't know why. I set up eth0 with the correct dns server. Rebooted, and boom. its back to the 127 (incorrect address).
MCC. How exactly do I get into that? I'm sorry for being dense, but this is rather frusterating. I'm not used to not being able to figure things out the first time around.
Originally posted by opjose MCC is the Mandrake Control Center
You said you "set up eth0"
what did you use to do this?
I just realized what you meant. Yes, I used MCC.
I went to MCC -> Hardware -> hardware -> ethernet card -> run config tool
I chose LAN connection, then is asks for Net Device my choices are eth0: Realtek, and manual choice.
I chose eth0. Then I chose manual configuration, kepy my IP setting and then I see my incorrect dns settings. I changed it and had the X server blow up on me.
Originally posted by opjose If X is not working, go ahead and re-install the drivers to get X up again.
BTW: after you re-install the driver RPM's see if any changes have been made to /etc/resolv.conf
THIS SHOULD READ:
----------------------------------------
2) Copy resolv.conf to a backup.
as root
cp /etc/resolv.conf /etc/resolv.conf.sav
3) Now edit /etc/rc.d/rc.local and add this line to it at the end.
cp -f /etc/resolv.conf.sav /etc/resolv.conf
Note the slashes and periods.
Hmm. To me that solution is a band-aid. Is there another way to do it? What if my ISP changes DNS servers and I have to change it? then I have to edit that crazy sav file.
After I install the nvidia driver its back to the 127 address. What I would like to do, is switch the DNS servers correctly, and knowing that X wont' start, reconfigure it such that it will. Is that porribls?
Originally posted by Snump Hmm. To me that solution is a band-aid. Is there another way to do it? What if my ISP changes DNS servers and I have to change it? then I have to edit that crazy sav file.
After I install the nvidia driver its back to the 127 address. What I would like to do, is switch the DNS servers correctly, and knowing that X wont' start, reconfigure it such that it will. Is that porribls?
According to your first post, your not using your ISP's DNS servers. Your using the IP of your router which is dynamically getting the nameserver info from your ISP.
Originally posted by Snump Hmm. To me that solution is a band-aid. Is there another way to do it? What if my ISP changes DNS servers and I have to change it? then I have to edit that crazy sav file.
After I install the nvidia driver its back to the 127 address. What I would like to do, is switch the DNS servers correctly, and knowing that X wont' start, reconfigure it such that it will. Is that porribls?
Aren't you setting a STATIC IP for your eth0 interface?
I thought this is what you were doing all along.
Anytime you have a static IP you need to manually set the ISP's DNS servers.
These are automatically set only if you are using DHCP and are DIRECTLY connected to the cable modem/dsl line.
What is a bit troubling is that the driver itself is reverting /etc/resolv.conf back to the 127.0.0.1 setting.
Are you using the .RPM file which came with the distro, or did you download a new driver from Nvidia?
Originally posted by darthtux According to your first post, your not using your ISP's DNS servers. Your using the IP of your router which is dynamically getting the nameserver info from your ISP.
Exactly.
However somehow his resolv.conf file's first entry keeps getting changed back to the local host.
Since any attempts to browse the net cause the search to start via a non existant local server, he gets a slow response/timeout before it moves on to quering the router, which also appears to be slow at forwarding the resolution requests.
Once he changes /etc/resolv.conf to point to the ISP's DNS, everything is fine.
So, either he fixes his router to have the router dole out the ISP's DNS (but this does not overcome the 127.0.0.1 issue), he installs BIND locally with the namecaching server RPM's, so that his local 127.0.01 CAN answer queries, or he finds what is modifying resolv.conf by tracking down the startup scripts.
Given what he has been through, installing the bind RPM's and the namecaching server RPM's is probably the easiest solution.
Originally posted by opjose Aren't you setting a STATIC IP for your eth0 interface?
I thought this is what you were doing all along.
Anytime you have a static IP you need to manually set the ISP's DNS servers.
These are automatically set only if you are using DHCP and are DIRECTLY connected to the cable modem/dsl line.
What is a bit troubling is that the driver itself is reverting /etc/resolv.conf back to the 127.0.0.1 setting.
Are you using the .RPM file which came with the distro, or did you download a new driver from Nvidia?
OK, my router can double as a DNS server. On the windows machines I have my router set as the DNS server and they're all working perfectly. maybe I shouldchange that.
I am using a driver downloaded from nvidia. I have to do a sh driverfile.run to install it. It is not an RPM.
I am using STATIC IPs. Nothing is dynamic.
What I want to do, is be able to set the DNS server setting, and have it stick. Thats it.
Most likely while I was sertting up the PC I typed it in wrong. If I remember correctly, for some stupid reason the default setting for the DNS servers was 127.0.0.1. I probably forgot to change number 1 and only changed 2 and 3 thus leaving the incorrect 127 in there. This PC was always slow at bringing up webpages. I just noticed it now because I was only using it to store files. now I want to use it for a few other things and I need DNS working correctly.
However somehow his resolv.conf file's first entry keeps getting changed back to the local host.
Since any attempts to browse the net cause the search to start via a non existant local server, he gets a slow response/timeout before it moves on to quering the router, which also appears to be slow at forwarding the resolution requests.
Once he changes /etc/resolv.conf to point to the ISP's DNS, everything is fine.
So, either he fixes his router to have the router dole out the ISP's DNS (but this does not overcome the 127.0.0.1 issue), he installs BIND locally with the namecaching server RPM's, so that his local 127.0.01 CAN answer queries, or he finds what is modifying resolv.conf by tracking down the startup scripts.
Given what he has been through, installing the bind RPM's and the namecaching server RPM's is probably the easiest solution.
I want to track down what is changing my resolf.conv.
Nothing in my internal network is dtnamic. everything is static.
No IP addys are being dished out by the router. So the router should be OK.
I just want to get these settings to stick.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.