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

[agoats]

If you have an ISP, you might look for their nameserver and use it in 
resolve.conf  .

Because of power failures or rebooting a different OS and coming back, I 
noticed that resolve.conf was changed from time to time, eliminating 
what worked. The solution was to copy resolve.conf to another file name 
and then later copy it back. This kept a good nameserver up. I tried 
making resolve.conf read only, but that didn't help either, protection 
got changed whenever I restarted.

Just FYI,

Alvin

Larry D'Agostino wrote:
>  
> Actually yes and no.  Alvin's suggestions I think did work with adding public 
> domain name servers.  But it doesn't work all the time.  I'm still baffled.  
> It really should work most of the time.
> 
> As I said before this is only a recent thing.  This was never a problem for me 
> until a few weeks ago.
> 
> I was wondering if updating to Suse 10.1 would help.
> 
> 
> On Friday 10 November 2006 12:10 am, Robert Pearson wrote:
>> On 11/4/06, Larry D'Agostino <larrydag at sbcglobal.net> wrote:
>>> I've been having problems recently with my opensuse 10.0 machine.  I
>>> really can't figure out why it is having such a hard time resolving some
>>> domains with either Firefox or Konqueror.  I can't even get to google.  I
>>> have tried the ip6 thing but that didn't work.  I popped in a Knoppix CD
>>> and it is able to resolve google just fine.  So I am left with it being a
>>> problem with Suse. I think it might have been some sort of update patch
>>> but how in the world would I know which one could it have been?
>>>
>>> My box is a Atlhon XP type machine connected to a Netgear WGT624
>>> router/firewall.  I use ATT Yahoo DSL and all hardware is connected by
>>> ethernet.
>> Any success? Or did it just come to an unresolved end?
>>
>> _______________________________________________
>> http://www.ntlug.org/mailman/listinfo/discuss
>