Created attachment 340634 [details] strace output of traceroute login.facebook.com Description of problem: I've been experiencing time outs while trying to connect to login.facebook.com and some other sites.. ( seems to be site or fqdn specific ) Now both traceroute and the host command seem to be affected by this well odd behaviour which suggest some common element they both use ( not traceroute nor the host command ) and hopefully we can flush this bug out in the open.. When I run traceroute login.facebook.com it takes traceroute about 20 to 25 seconds to display the the first ( 1 ) entry vs it works immediately when running traceroute facebook.com. When running host login.facebook.com it shows the ip address for login.facebook.com then errors out with ";; connection timed out; no servers could be reached" Now ping and dig response very well.. Version-Release number of selected component (if applicable): latest rawhide as of the date filing this bug. How reproducible: Always when running traceroute login.facebook.com and host login.facebook.com Steps to Reproduce: 1. the above. 2. 3. Actual results: Weirdness Expected results: Happyness Additional info:
Created attachment 340636 [details] strace output of traceroute facebook.com for comparison
Created attachment 340637 [details] strace output of host login.facebook.com
Created attachment 340639 [details] strace output of host facebook.com for comparison
Created attachment 340640 [details] time dig output
Created attachment 340641 [details] time ping output
Created attachment 340642 [details] time host output
Created attachment 340643 [details] time traceroute output
Oh yeah I forgot.. http://www.smolts.org/client/show/pub_29f00f44-9a40-4e29-84d5-75fedd098e35
Duplicated on Debian and f10 looks like it's an broken dns setup on facebooks half.. Closing..