[NBLUG/talk] Changed Network

[Walter Hansen]

both nslookup and dig are instant in their responses.

lynx won't resolve www.sonic.net just like mozilla on ethior machine.

The only change was going from the 192.168.0 network to the 192.168.33
network. Everything was rebooted.

[root at amanda etc]# cat hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
#servers

#ivr boxes

127.0.0.1       amanda  localhost       localhost.localdomain
192.168.33.211  amanda  amanda.corporate-image.com
192.168.33.210  clara
192.168.33.220  mabel
192.168.33.100  router

[root at amanda etc]#

[root at amanda sysconfig]# cat network
NETWORKING=yes
HOSTNAME=amanda
GATEWAY=router


[root at amanda network-scripts]# cat ifcfg-eth0
DEVICE=eth0
BOOTPROTO=none
BROADCAST=192.168.33.255
IPADDR=192.168.33.211
NETMASK=255.255.255.0
NETWORK=192.168.33.0
ONBOOT=yes
USERCTL=no
PEERDNS=no
TYPE=Ethernet
GATEWAY=192.168.33.100
[root at amanda network-scripts]#


>
>> Yep. That takes me there like a lightning bolt.
>>
>> > What if you point mozilla at 209.204.190.64 (www.sonic.net) ?
>
> If (as I understand you to say) browsing to www.sonic.net is slow
> but browsing to 209.204.190.64 (the IP of www.sonic.net) is fast,
> then you (almost certainly) have a DNS (Domain Name Service) issue.
>
> What can you see (and, how quickly?) at the commandline, via
> nslookup/dig/whatever?
>
> Check DNS service, but also look into the browser config's...
> some browsers can specify something unexpected.  If you're proxying, the
> error may be on a proxy-server; etc.
>
>
> - Steve S.
>
>
>
>
> _______________________________________________
> talk mailing list
> talk at nblug.org
> http://nblug.org/cgi-bin/mailman/listinfo/talk