apt-get will not resolv address

CNBarnes · 06-21-2010, 01:58 AM

apt-get and ssh are now all of a sudden not resolving hostnames, but strangley enough, ping will.

# ping ftp.us.debian.org
PING ftp.us.debian.org (64.50.236.52) 56(84) bytes of data.
64 bytes from ftp-chi.osuosl.org (64.50.236.52): icmp_seq=1 ttl=53 time=37.6 ms

# apt-get update
Err http://volatile.debian.org lenny/volatile Release.gpg
Could not resolve 'volatile.debian.org'

This was working just SECONDS ago. What's more - it works from another computer on the same network (using the exact same resolv.conf file).

saifkhan123 · 06-21-2010, 02:18 AM

make sure that your /etc/resolve.conf contains the valid nameservers and redundancy should be there (define multiple dns servers).

kumar.manoj412 · 06-21-2010, 03:00 AM

Try appending this line to your /etc/hosts file

130.89.149.227 volatile.debian.org

Quote:

Originally Posted by CNBarnes

apt-get and ssh are now all of a sudden not resolving hostnames, but strangley enough, ping will.

# ping ftp.us.debian.org
PING ftp.us.debian.org (64.50.236.52) 56(84) bytes of data.
64 bytes from ftp-chi.osuosl.org (64.50.236.52): icmp_seq=1 ttl=53 time=37.6 ms

# apt-get update
Err http://volatile.debian.org lenny/volatile Release.gpg
Could not resolve 'volatile.debian.org'

This was working just SECONDS ago. What's more - it works from another computer on the same network (using the exact same resolv.conf file).

CNBarnes · 06-22-2010, 01:56 PM

Actually, we were trying to install the pam-ldap authentication, which required some changes to /etc/nsswitch.conf (and we didn't have it correct). Apparently nsswitch.conf does it's own DNS functions (and in a not-so-nice way).