Name Resolution Issue from Browser only, on Debian 5.0.4
Hi All,
I am facing a rather peculiar issue. I installed Debian 5.0.4 on my laptop. The basic network connectivity works fine, and the DHCP client daemon seems to have picked up the right config info from my DSL router. But, anything related to HTTP does not work - browser, WGET, etc.
This is what my output looks like:
----------------------------------------------------------------------
hchandra@hchandra-lap:~$ cat /etc/resolv.conf
### BEGIN INFO
#
# Modified_by: NetworkManager
# Process: /usr/bin/NetworkManager
# Process_id: 2988
#
### END INFO
nameserver 192.168.1.1
nameserver 192.168.1.1
hchandra@hchandra-lap:~$ ping ftp.debian.org
PING ftp.debian.org (130.89.149.226) 56(84) bytes of data.
64 bytes from ftp.debian.org (130.89.149.226): icmp_seq=1 ttl=50 time=213 ms
64 bytes from ftp.debian.org (130.89.149.226): icmp_seq=2 ttl=50 time=213 ms
64 bytes from ftp.debian.org (130.89.149.226): icmp_seq=3 ttl=50 time=212 ms
^C
--- ftp.debian.org ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 212.532/213.114/213.558/0.430 ms
hchandra@hchandra-lap:~$ ftp ftp.debian.org
Connected to ftp.debian.org.
220 ftp.debian.org FTP server
Name (ftp.debian.org:hchandra): anonymous
331 Please specify the password.
Password:
230 Login successful.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> bye
221 Goodbye.
hchandra@hchandra-lap:~$ wget http://www.debian.org
--2010-02-20 17:38:08-- http://www.debian.org/
Resolving www.debian.org... 1.0.0.0
Connecting to www.debian.org|1.0.0.0|:80... ^C
hchandra@hchandra-lap:~$ wget --no-dns-cache http://www.debian.org/
--2010-02-20 17:43:26-- http://www.debian.org/
Resolving www.debian.org... 1.0.0.0
Connecting to www.debian.org|1.0.0.0|:80... ^C
hchandra@hchandra-lap:~$
----------------------------------------------------------------------
>From this, it should be obvious that ping & ftp are able to resolve the DNS names correctly, but WGET and any browser resolve it to '1.0.0.0'.
Can anyone tell me what the problem could be? What is the difference between the way ping & ftp resolve names and the way wget and browsers do so?
Regards,
Hemanth
Reply to: