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

[agoats]

Either reboot or restart all of your services. For most people, it's 
easier to reboot and since I'm not familiar with the distribution you're 
using, reboot is the simplest and safest.

When the network services start up, they check files like the 
resolv.conf and rarely go back to it.

I had a similar problem some years ago when CompuServe changed their 
servers due to spam and various attacks. Their nameserver changed and 
how it was accessed. You either used windows or had problems. I found a 
public nameserver and used it, which fixed all of my problems. But I did 
have to some major restarting of services or reboot.

Alvin


Larry D'Agostino 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?
> 
> 
> On Monday 06 November 2006 11:32 pm, Robert Pearson wrote:
>> On 11/6/06, Larry D'Agostino <larrydag at sbcglobal.net> wrote:
>>> Well here goes.  Thanks for the feedback Robert.  I'm still a bit
>>> baffled.
>>>
>>> I have tried adding the nameservers to my resolv.conf file but it seems
>>> that doesn't help either.  I'm not sure why.  I can ping the nameservers
>>> no problem.
>>>
>>> Here is an nslookup of google.com against nameserver.  it seems to work
>>> OK.
>>>
>>> Server:         68.94.156.1
>>> Address:        68.94.156.1#53
>>>
>>> Non-authoritative answer:
>>> Name:   google.com
>>> Address: 64.233.167.99
>>> Name:   google.com
>>> Address: 64.233.187.99
>>> Name:   google.com
>>> Address: 72.14.207.99
>>>
>>> Yet putting google in my browser doesn't resolve.
>> What did you get when tried Robert at thorshammer.org suggestion of
>> "If that works then try the IP of your netgear box."?
>>
>>> Here is my resolv.conf file.  Notice it shows my netgear IP 192.168.0.1
>>> which is correct.
>>>
>>> ### BEGIN INFO
>>> #
>>> # Modified_by:  dhcpcd
>>> # Backup:       /etc/resolv.conf.saved.by.dhcpcd.eth0
>>> # Process:      dhcpcd
>>> # Process_id:   4353
>>> # Script:       /sbin/modify_resolvconf
>>> # Saveto:
>>> # Info:         This is a temporary resolv.conf created by service
>>> dhcpcd. #               The previous file has been saved and will be
>>> restored later. #
>>> #               If you don't like your resolv.conf to be changed, you
>>> #               can set MODIFY_{RESOLV,NAMED}_CONF_DYNAMICALLY=no. This
>>> #               variables are placed in /etc/sysconfig/network/config.
>>> #
>>> #               You can also configure service dhcpcd not to modify it.
>>> #
>>> #               If you don't like dhcpcd to change your nameserver
>>> #               settings
>>> #               then either set DHCLIENT_MODIFY_RESOLV_CONF=no
>>> #               in /etc/sysconfig/network/dhcp, or
>>> #               set MODIFY_RESOLV_CONF_DYNAMICALLY=no in
>>> #               /etc/sysconfig/network/config or (manually) use dhcpcd
>>> #               with -R.  If you only want to keep your searchlist, set
>>> #               DHCLIENT_KEEP_SEARCHLIST=yes in
>>> /etc/sysconfig/network/dhcp or #               (manually) use the -K
>>> option.
>>> #
>>> ### END INFO
>>> search site site site
>>> nameserver 192.168.0.1
>> ...snip...
>>
>> My /etc/resolv.conf only works when the ending lines contain this
>> information:
>>
>> ### END INFO
>> search tx.rr.com
>> nameserver 24.93.41.125
>> nameserver 24.93.41.126
>>
>> Take away the two "nameserver" lines and I can't resolve anything.
>> This is what happens when my Broadband line or Linksys router is down
>> at boot time.
>> DHCP writes an /etc/resolv.conf with only the "search" line in it.
>> Those two nameservers and IP addresses are automatically supplied by my
>> ISP.
>>
>> I run only workstations. I do not know about servers for sure.
>> You did say that this worked until just recently and we don't know what
>> changed. We''ll just have to fix it the hard way.
>>
>> ...snip...
>>
>> Alvin's suggestion makes sense. Try one at a time of those as Alvin
>> suggests.
>>
>> Another suggestion is to put the Knoppix CD in again and look at its
>> /etc/resolv.conf to see what works for it.
>>
>> _______________________________________________
>> http://www.ntlug.org/mailman/listinfo/discuss
>