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 darthtux Your router gets it's IP and DNS information dynamically from your ISP unless you payed for a static IP.
Two of us have already stated, your going to have to go and search through your startup scripts and find out where it is setting the 127.0.0.1.
Yes, my router gets its IP onformation from the WAN side dynamically. I am giving my internal PCs the INTERNAL IP address of the router as the DNS servers.
I am studying DNS and so I installed bind on my box. Now I have
nameserver 127.0.0.1
in my /etc/resolv.conf
I'm using Debian and found the cause in my startup script for bind. So that is where you need to look. Somewhere in /etc/init.d or on of the /etc/rc?.d directories. I am not sure where Mandrake keeps them.
Running bind as a caching server has speeded up my internet surfing. I can tell the differnce in speed from the first time I visit a site and subsequent visits.
The only reason I could think of why the Nvidia/X installer would be so dependant upon /etc/resolv.conf, would be if your machine otherwise did not know it's own name!
That is you didn't NAME the nic interfaces and/or correctly specify the hostname and domain.
Try setting /etc/resolv.conf as you had it before with the working IP's for surfing.
Then ping "localhost", "ping MyHostname" and "ping MyHostname.fulldomain.com".
All should respond to the ping, usually with the latter two returning the IP of the NIC.
If NOT you will need to edit /etc/hosts and try again until the ping works.
This will probably fix the problem with X dying after you change /etc/resolv.conf.
opjose, looks like you have started me on another project I think I will try to do it by hand. I like to get down and dirty with the configs If you know of any sites besides the squid home page that might come in handy, please post them.
BTW, my caching server is woking great. First query is 94 msec. The subsequent ones are 7msec. What an improvement!
Originally posted by opjose This had me thinking...
The only reason I could think of why the Nvidia/X installer would be so dependant upon /etc/resolv.conf, would be if your machine otherwise did not know it's own name!
That is you didn't NAME the nic interfaces and/or correctly specify the hostname and domain.
Try setting /etc/resolv.conf as you had it before with the working IP's for surfing.
Then ping "localhost", "ping MyHostname" and "ping MyHostname.fulldomain.com".
All should respond to the ping, usually with the latter two returning the IP of the NIC.
If NOT you will need to edit /etc/hosts and try again until the ping works.
This will probably fix the problem with X dying after you change /etc/resolv.conf.
OK, I forget where exactly I have to enter that information....
This gets better and better. I reformatted. Just for the heck ofit. WhenI go into my network settings like I did previously, X refuses to start. I changed nothing. I looked inthere to make sure it was not resetting again on boot, and boom. I reboot and it says X can't start. Arg.
Prior to your reformat it seems that you had some entries in netprofiles which might have been setting things back.
Anyway start up in non-fb mode which will get you a TEXT startup.
Login as root.
Now change /etc/resolv.conf to what you had when it was working and type "X".
See if you get a graphical screen (ALT-BACKSPACE gets you back out...)
If you do then do as I mentioned in the prior post.
I still believe that one problem you are having is that the machine does not know who it is.
If you cannot get the graphical screen try running XorgConfig or whatever it is called and try different video card and monitor settings (test each one!) until you get something that works.
Originally posted by opjose Prior to your reformat it seems that you had some entries in netprofiles which might have been setting things back.
Anyway start up in non-fb mode which will get you a TEXT startup.
Login as root.
Now change /etc/resolv.conf to what you had when it was working and type "X".
See if you get a graphical screen (ALT-BACKSPACE gets you back out...)
If you do then do as I mentioned in the prior post.
I still believe that one problem you are having is that the machine does not know who it is.
If you cannot get the graphical screen try running XorgConfig or whatever it is called and try different video card and monitor settings (test each one!) until you get something that works.
It appears I have discovered a bug.
After a completely clear reformat, installing no servers at all, when I boot into Gnome of KDE for the first time, that 127 DNS entry is there. I disabled that hotplugging thing, and it still does it.
Change it once, reboot and its back. I tried changing it everywhere, through various ways, and Its still there.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.