macondo wrote: > # cat /etc/resolv.conf > search cpe.cableonda.net > nameserver 200.75.200.2 > nameserver 200.75.200.3 > ping: unknown host ftp.debian.org It really looks like something in your dns resolver system is broken. There are several pieces of it. All must work. But it is unusual for them to be broken because people don't usually break those files. I can't check those nameservers because they are refusing me. I would like to check them and verify that they can resolve ftp.debian.org. Here is what I get when I try. This isn't unusual since I am outside trying to query them. They are your dhcp configured nameservers and should work for you. $ host ftp.debian.org 200.75.200.2 Using domain server: Name: 200.75.200.2 Address: 200.75.200.2#53 Aliases: Host ftp.debian.org.proulx.com not found: 5(REFUSED) Here is a working example: $ host ftp.debian.org 8.8.8.8 Using domain server: Name: 8.8.8.8 Address: 8.8.8.8#53 Aliases: ftp.debian.org has address 130.89.148.12 ftp.debian.org has IPv6 address 2001:610:1908:b000::148:12 ftp.debian.org mail is handled by 0 . Trying to guess correctly why that is broken for you is difficult because things can be broken in a large number of ways. Have you changed /etc/nsswitch.conf? Look at the contents and tell us if they are different from this: $ grep host /etc/nsswitch.conf hosts: files dns It would be unusual for that to be different (unless NIS/YP or something is installed) but breaking that file could definitely break the DNS resolver. I would be inclined to test a solution by editing /etc/resolv.conf and setting exactly one nameserver line like this: nameserver 8.8.8.8 And with that in place then see if you can then resolve ftp.debian.org. Should work. $ ping -c 3 ftp.debian.org PING ftp.debian.org (130.89.148.12) 56(84) bytes of data. 64 bytes from klecker2.snt.utwente.nl (130.89.148.12): icmp_req=1 ttl=43 time=167 ms 64 bytes from klecker2.snt.utwente.nl (130.89.148.12): icmp_req=2 ttl=43 time=215 ms 64 bytes from klecker2.snt.utwente.nl (130.89.148.12): icmp_req=3 ttl=43 time=531 ms --- ftp.debian.org ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 167.112/304.926/531.724/161.605 ms If it doesn't then keep looking. > W: Failed to fetch http://ftp.us.debian.org/ > debian/dists/wheezy/InRelease > Could not resolve 'ftp.us.debian.org wheezy Release.gpg That error is a descriptive error message. But the next part does not make sense to me. > Could not resolve 'debian.net' > Err http://debian.net wheezy Release.gpg > Err http:// debian.net wheezy InRelease What is that "debian.net" "http:// debian.net" doing there? Those don't seem possible given the data you have provided so far. Please be accurate. The difference between debian.org, ftp.debian.org, debian.net, " debian.net" are important and mistakes there can lead to endless confusion. I can't help but think that part of the problem is inaccurate details. Bob
Attachment:
signature.asc
Description: Digital signature