[NTLUG:Discuss] browser can't resolve some domain names, including google.com
Robert Pearson
e2eiod at gmail.com
Sat Nov 11 05:00:27 CST 2006
On 11/10/06, Larry D'Agostino <larrydag at sbcglobal.net> 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.
I think that is a great idea!
I was running 10.0 and had about decided my motherboard was bad because
my USB performance was slower than USB1.1.
Taking a chance I upgraded to 10.1 and all the problems went away!
I have been very happy with 10.1. It is as solid as 9.3, my previous favorite.
YMMV.
You might want to keep Alvin's DNS suggestion in mind.
I decided not to have my Linksys router do DNS for me.
My machine is a workstation, not a server. It might make a difference.
I wanted the DNS IPs behind the Firewall and supplied by the ISP. I
felt the Linksys was more easily hacked.
I wish I knew the answers to these questions.
More information about the Discuss
mailing list