kubuntu host resolving problem

calanor · 08-28-2009, 09:12 AM

i can not update kubuntu or install anything, i get the error cannot resolve archive.ubuntu.com,i use internet through our college proxy,
i am able to surf in konquerer but it can't open gmail,its all fine when i use songbird,
i posted this problem in kubuntuforums.net and a member told me to add hosts (or whatever they are called) to resolv.conf and i did, it didn't solve the problem and i restarted to find those entries were deleted
and now it looks like:
# Generated by NetworkManager
domain juitw.org
search juitw.org
nameserver 172.16.73.20
nameserver 172.16.73.3
nameserver 172.16.73.4

the same problem happens at home although there is broadband connection i mean no proxies
i am using kubuntu 9.04 jaunty and no packages installed other than what came in the cd except songbird

evilted · 08-28-2009, 09:26 AM

the resolve.conf should contain entries for dns servers. are the nameservers you entered actual dns servers? you can try opendns' nameservers: 208.67.222.222 and 208.67.220.220

what happens when you try to ping it?

Code:

ping archive.ubuntu.com
PING archive.ubuntu.com (91.189.88.140) 56(84) bytes of data.
64 bytes from jackass.canonical.com (91.189.88.140): icmp_seq=1 ttl=55 time=108 ms
64 bytes from jackass.canonical.com (91.189.88.140): icmp_seq=2 ttl=55 time=104 ms
64 bytes from jackass.canonical.com (91.189.88.140): icmp_seq=3 ttl=55 time=103 ms
^C
--- archive.ubuntu.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 103.634/105.641/108.342/2.018 ms

calanor · 08-28-2009, 09:34 AM

i get
ping: unknown host archive.ubuntu.com

repo · 08-28-2009, 09:36 AM

Try to use open dns
put these in your resolv.conf

Code:

nameserver 208.67.220.220
nameserver 208.67.222.222

calanor · 08-28-2009, 09:39 AM

ok now it looks like
# Generated by NetworkManager
domain juitw.org
search juitw.org
nameserver 172.16.73.20
nameserver 172.16.73.3
nameserver 172.16.73.4
nameserver 208.67.220.220
nameserver 208.67.222.222

and i still cannot ping ubuntu.com

repo · 08-28-2009, 09:42 AM

You should add the dns in the settings from networkmanager.
AFAIK networmanager overwrites them.
Remove the old ones and use open dns

calanor · 08-28-2009, 09:45 AM

and how exactly do i do that

repo · 08-28-2009, 09:49 AM

Take a look at
http://www.thejackol.com/2008/05/20/...dy-herongutsy/

evilted · 08-28-2009, 09:53 AM

Quote:

Originally Posted by calanor

ok now it looks like
# Generated by NetworkManager
domain juitw.org
search juitw.org
nameserver 172.16.73.20
nameserver 172.16.73.3
nameserver 172.16.73.4
nameserver 208.67.220.220
nameserver 208.67.222.222

and i still cannot ping ubuntu.com

you only need the following entries in your resolve.conf; it should look like:

Code:

nameserver 208.67.220.220
nameserver 208.67.222.222

obviously the ip's on the 172.16.73.x network are not dns servers, so you should be able to remove them...

can you ping an ip on a remote network?

Code:

 ping 208.67.220.220
PING 208.67.220.220 (208.67.220.220) 56(84) bytes of data.
64 bytes from 208.67.220.220: icmp_seq=1 ttl=55 time=136 ms
64 bytes from 208.67.220.220: icmp_seq=2 ttl=55 time=136 ms
64 bytes from 208.67.220.220: icmp_seq=3 ttl=55 time=140 ms
64 bytes from 208.67.220.220: icmp_seq=4 ttl=55 time=140 ms
^C
--- 208.67.220.220 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 136.489/138.539/140.813/1.939 ms

calanor · 08-28-2009, 09:59 AM

dear god nothing works
i used opensuse 11.1 and everything worked except kde
so i switched and now i get this

calanor · 08-28-2009, 10:06 AM

yes i can ping 208.67.220.220
but it says 100% packet loss

evilted · 08-28-2009, 10:16 AM

Quote:

Originally Posted by calanor

yes i can ping 208.67.220.220
but it says 100% packet loss

if you got 100% packet loss then you cant ping!!!

now you need to make sure your network is configured correctly..

please post the output of

Code:

ifconfig
route
ip route
tracert -d 208.67.220.220

the reason it worked before is becuaes your network was configured correctly. something is wrong with it now!

calanor · 08-28-2009, 11:42 AM

a friend of mine is using ubuntu 9.04 and he has the same contents in resolv.conf as i had before and its all working out for him

ifconfig:
eth0 Link encap:Ethernet HWaddr 00:1c:c0:0f:4e:f7
inet addr:172.16.16.57 Bcast:172.16.17.255 Mask:255.255.254.0
inet6 addr: fe80::21c:c0ff:fe0f:4ef7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9256 errors:0 dropped:0 overruns:0 frame:0
TX packets:522 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1044238 (1.0 MB) TX bytes:72245 (72.2 KB)
Memory:90300000-90320000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1240 (1.2 KB) TX bytes:1240 (1.2 KB)

route:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
172.16.16.0 * 255.255.254.0 U 1 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
default 172.16.16.1 0.0.0.0 UG 0 0 0 eth0

ip route:
172.16.16.0/23 dev eth0 proto kernel scope link src 172.16.16.57 metric 1
169.254.0.0/16 dev eth0 scope link metric 1000
default via 172.16.16.1 dev eth0 proto static

tracert -d 208.67.220.220:
The program 'tracert' is currently not installed. You can install it by typing:
sudo apt-get install traceroute
bash: tracert: command not found

calanor · 08-28-2009, 11:42 AM

a friend of mine is using ubuntu 9.04 and he has the same contents in resolv.conf as i had before and its all working out for him

ifconfig:
eth0 Link encap:Ethernet HWaddr 00:1c:c0:0f:4e:f7
inet addr:172.16.16.57 Bcast:172.16.17.255 Mask:255.255.254.0
inet6 addr: fe80::21c:c0ff:fe0f:4ef7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9256 errors:0 dropped:0 overruns:0 frame:0
TX packets:522 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1044238 (1.0 MB) TX bytes:72245 (72.2 KB)
Memory:90300000-90320000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1240 (1.2 KB) TX bytes:1240 (1.2 KB)

route:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
172.16.16.0 * 255.255.254.0 U 1 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
default 172.16.16.1 0.0.0.0 UG 0 0 0 eth0

ip route:
172.16.16.0/23 dev eth0 proto kernel scope link src 172.16.16.57 metric 1
169.254.0.0/16 dev eth0 scope link metric 1000
default via 172.16.16.1 dev eth0 proto static

tracert -d 208.67.220.220:
The program 'tracert' is currently not installed. You can install it by typing:
sudo apt-get install traceroute
bash: tracert: command not found

evilted · 08-28-2009, 11:46 AM

only question: is your subnet correct? you have 255.255.254.0 (/23)... a normal (!?!) /24 subnet is 255.255.255.0