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

[Robert Pearson]

On 11/8/06, Larry D'Agostino <larrydag at sbcglobal.net> wrote:
> Results with nslookup google.com (with Netgear IP).  seems to work.  still
> baffled.
>
> Server:         192.168.0.1
> Address:        192.168.0.1#53
>
> Non-authoritative answer:
> Name:   google.com
> Address: 64.233.187.99
> Name:   google.com
> Address: 72.14.207.99
> Name:   google.com
> Address: 64.233.167.99
>
> I tried Alvins recommendation.  Didn't work after shutting down yast.  Do i
> need to reboot?

Where resolving the problem stands.
Using Robert at thorshammer.org suggestion, your system seems to resolve
fine using the Netgear nameserver.
Except when you submit the name to resolve in Firefox or Konqueror.
To me this means a browser problem.
Something that affects all browsers would be at the system level?
And it worked until recently. The only recent changes have been updates.

Does 192.168.0.1 resolve to access the Netgear from both Firefox and
Konqueror for maintenance?

...snip...