Re: Name Resolution Issue from Browser only, on Debian 5.0.4
Camaleón,
Thank you for replying to my mail. My replies inline...
On Tue, February 23, 2010 21:30:51 +0530, Camaleón wrote:
>
>On Tue, 23 Feb 2010 00:30:15 -0800, Hemanth M. C. wrote:
>
>> 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.
>
>Does this help?
>
>WGET can’t resolve host
>http://serverfault.com/questions/76421/wget-cant-resolve-host
The solution mentioned in the link does not work for me, since my installation is a new installation - I did not touch the nsswitch.conf file. However, the answer seems to lie somewhere there. I played around with the nsswitch.conf file, but was unable to make it resolve correctly. This is the file:
--------------------------------------------------------------------------------
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.
passwd: compat
group: compat
shadow: compat
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
--------------------------------------------------------------------------------
I learnt a lot about this file from the man pages, but was unable to figure out what mdns4 and mdns4_minimal are. I will try to play around with this for some more time, but would appreciate any input on this issue from anybody.
Meanwhile, I got some more details on the quirky behaviour:
--------------------------------------------------------------------------------
hchandra@hchandra-lap:~$ wget http://www.ibm.com/
--2010-02-24 08:48:43-- http://www.ibm.com/
Resolving www.ibm.com... 1.0.0.0
Connecting to www.ibm.com|1.0.0.0|:80... ^C
hchandra@hchandra-lap:~$ getent hosts www.ibm.com
1.0.0.0 www.ibm.com
hchandra@hchandra-lap:~$ ping www.ibm.com
PING www.ibm.com.cs186.net (129.42.56.216) 56(84) bytes of data.
^C
--- www.ibm.com.cs186.net ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1013ms
hchandra@hchandra-lap:~$ getent hosts www.ibm.com
129.42.56.216 www.ibm.com
hchandra@hchandra-lap:~$ wget http://www.ibm.com/
--2010-02-24 08:49:19-- http://www.ibm.com/
Resolving www.ibm.com... 129.42.56.216
Connecting to www.ibm.com|129.42.56.216|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.ibm.com/in/ [following]
--2010-02-24 08:49:20-- http://www.ibm.com/in/
Reusing existing connection to www.ibm.com:80.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://www.ibm.com/in/en/ [following]
--2010-02-24 08:49:20-- http://www.ibm.com/in/en/
Reusing existing connection to www.ibm.com:80.
HTTP request sent, awaiting response... 200 OK
Length: 31696 (31K) [text/html]
Saving to: `index.html.2'
100%[======================================>] 31,696 46.1K/s in 0.7s
2010-02-24 08:49:22 (46.1 KB/s) - `index.html.2' saved [31696/31696]
--------------------------------------------------------------------------------
In short, pinging a certain destination helps the getent and wget commands resolve the name correctly. Why is this so? Are the DNS lookups cached somewhere? Does this cache have to be cleared?
Thank you,
Regards,
Hemanth
Reply to: