Bug 496979

Summary: Weird behaviour for both traceroute and the host command
Product: [Fedora] Fedora Reporter: Jóhann B. Guðmundsson <johannbg>
Component: tracerouteAssignee: Dmitry Butskoy <dmitry>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: dmitry, jskala
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-04-21 22:20:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
strace output of traceroute login.facebook.com
none
strace output of traceroute facebook.com for comparison
none
strace output of host login.facebook.com
none
strace output of host facebook.com for comparison
none
time dig output
none
time ping output
none
time host output
none
time traceroute output none

Description Jóhann B. Guðmundsson 2009-04-21 21:43:03 UTC
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:

Comment 1 Jóhann B. Guðmundsson 2009-04-21 21:44:59 UTC
Created attachment 340636 [details]
strace output of traceroute facebook.com for comparison

Comment 2 Jóhann B. Guðmundsson 2009-04-21 21:45:53 UTC
Created attachment 340637 [details]
strace output of host login.facebook.com

Comment 3 Jóhann B. Guðmundsson 2009-04-21 21:47:04 UTC
Created attachment 340639 [details]
strace output of host facebook.com for comparison

Comment 4 Jóhann B. Guðmundsson 2009-04-21 21:48:02 UTC
Created attachment 340640 [details]
time dig output

Comment 5 Jóhann B. Guðmundsson 2009-04-21 21:48:35 UTC
Created attachment 340641 [details]
time ping output

Comment 6 Jóhann B. Guðmundsson 2009-04-21 21:49:14 UTC
Created attachment 340642 [details]
time host output

Comment 7 Jóhann B. Guðmundsson 2009-04-21 21:52:58 UTC
Created attachment 340643 [details]
time traceroute output

Comment 8 Jóhann B. Guðmundsson 2009-04-21 21:56:55 UTC
Oh yeah I forgot.. 

http://www.smolts.org/client/show/pub_29f00f44-9a40-4e29-84d5-75fedd098e35

Comment 9 Jóhann B. Guðmundsson 2009-04-21 22:20:30 UTC
Duplicated on Debian and f10 looks like it's an broken dns setup on facebooks half.. Closing..