[NTLUG:Discuss] browser can't resolve some domain names, including google.com

Robert Pearson e2eiod at gmail.com
Sun Nov 5 23:38:19 CST 2006


On 11/5/06, Larry D'Agostino <larrydag at sbcglobal.net> wrote:
>
> resolv.conf shows the nameserver of my router (192.168....). I also added the
> nameservers of my ISP but that didn't help.

Did you reboot or restart the process that resolves the IP nameservers
after you added them? You can do this in YaST or direct.
I can't always recall off the top of my head what the process name is,
like now, so I just reboot. Check the /etc/resolv.conf after the
reboot to make sure it didn't get wiped out again.

Be advised this will happen with SUSE and once you get it working
again make a local copy of the working /etc/resolv.conf. Call it
/etc/resolv.conf-org-DSL or something like that. I always make a copy
of the working /etc/resolv.conf to /etc/resolv.conf-org as a backup.
Use copy (cp) to restore it so you don't lose your backup.

Do you have static IP's for your machine(s)?
Or do you run DHCP from your Netgear box?
Actually that won't make any difference at all. You get the same
effect if the Netgear is down as the DSL being down. The SUSE OS
writes a new /etc/resolv.conf with no nameservers in it.

The SUSE OS or the ISP will change your /etc/resolv.conf at will.
If the DSL line is down when you login SUSE will create a new
/etc/resolv.conf file with no nameservers in it because it couldn't
get a network connection to find any.
If you run DHCP there is an option to prevent DHCP from altering the
/etc/resolv.conf file at boot. Be advised it doesn't always work which
is why
on my SUSE machines I keep a backup copy of the /etc/resolv.conf file
after I know it is working.
I am constantly switching between DSL and Cable Modem depending on who
has the best price. I have one of each /etc/resolv.conf saved for each
ISP provider.



More information about the Discuss mailing list