Quote:
Originally posted by short101
I dont think you want that 127.0.0.1 line in there. In my resolve.conf all I have is two nameserver lines with my isp's dns machines adresses, under that is search. ie
nameserver 203.194.27.57
nameserver 203.194.56.150
search
If you have the 127.0.0.1 line, it will use your machine to resolve the adresses which it cant do. afaik.
Ring your isp and find out the numbers of there dns machines and only put those two in there and see how you go, if not post back.
What distro are you using.
If the above didnt work, can you post the contents of your
/etc/sysconfig/network file
|
I have done that ...it is still not working
here is /erc/sysconfig/network
NETWORKING=yes
HOSTNAME=localhost.localdomain
[root@localhost root]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0B
B:95:23:5A
inet addr:192.168.2.102 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3580 errors:0 dropped:0 overruns:0 frame:0
TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:354655 (346.3 Kb) TX bytes:6592 (6.4 Kb)
Interrupt:10 Base address:0x4000 Memory:e0204000-e0205080
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:12100 errors:0 dropped:0 overruns:0 frame:0
TX packets:12100 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:825524 (806.1 Kb) TX bytes:825524 (806.1 Kb)
[root@localhost root]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0
[root@localhost root]# ping 192.168.2.1
64 bytes from 192.168.2.1: icmp_seq=95 ttl=255 time=0.746 ms
64 bytes from 192.168.2.1: icmp_seq=96 ttl=255 time=0.758 ms
64 bytes from 192.168.2.1: icmp_seq=97 ttl=255 time=0.735 ms
[root@localhost root]# nslookup
http://www.yahoo.com
Note: nslookup is deprecated and may be removed from future releases.
Consider using the `dig' or `host' programs instead. Run nslookup with
the `-sil[ent]' option to prevent this message from appearing.
;; connection timed out; no servers could be reached