DNS issue on Fedora 12? wget wordpress.org fails where wget www.google.com works
Posted
by
Tom Auger
on Server Fault
See other posts from Server Fault
or by Tom Auger
Published on 2010-12-17T16:32:16Z
Indexed on
2010/12/26
23:55 UTC
Read the original article
Hit count: 326
I'm administering a Fedora 12 box, but am quite new to networking specifics. Recently one of our WordPress apps hosted on our server has stopped being able to perform its auto-update or auto-download of plugins.
Investigating further, I have tried the following:
$ wget wordpress.org
--2010-12-17 11:26:50-- http://wordpress.org/
Resolving wordpress.org... failed: Temporary failure in name resolution.
wget: unable to resolve host address âwordpress.orgâ
Whereas:
$ wget www.google.com
--2010-12-17 11:27:26-- http://www.google.com/
Resolving www.google.com... 74.125.226.82, 74.125.226.84, 74.125.226.80, ...
Connecting to www.google.com|74.125.226.82|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.google.ca/ [following]
--2010-12-17 11:27:26-- http://www.google.ca/
Resolving www.google.ca... 173.194.32.104
Connecting to www.google.ca|173.194.32.104|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: âindex.html.4â
[ <=> ] 9,079 --.-K/s in 0.02s
2010-12-17 11:27:26 (462 KB/s) - âindex.html.4â
Interestingly:
$ ping wordpress.org
PING wordpress.org (72.233.56.138) 56(84) bytes of data.
64 bytes from wordpress.org (72.233.56.138): icmp_seq=1 ttl=50 time=81.5 ms
64 bytes from wordpress.org (72.233.56.138): icmp_seq=2 ttl=50 time=67.3 ms
^C
--- wordpress.org ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1783ms
rtt min/avg/max/mdev = 67.361/74.448/81.536/7.092 ms
and
$ nslookup wordpress.org
Server: 192.168.2.1
Address: 192.168.2.1#53
Non-authoritative answer:
Name: wordpress.org
Address: 72.233.56.138
Name: wordpress.org
Address: 72.233.56.139
nscd has been stopped and flushed. iptables appear to be clean. At this point I have exhausted my limited abilities to diagnose the issue. Can anyone suggest a resolution path?
© Server Fault or respective owner