DNS: same IP, 2 different domains, 2 different routes

Posted on 2006-05-16
Last Modified: 2013-12-07
I have a server with several websites on it. If I trace route any of those domains, I get the same path as when I trace the IP ( Now if I trace, I get something totally different. The trace gets stuck in a loop at hop 19

19    70 ms    71 ms    73 ms []
20    70 ms    70 ms    70 ms []
21    97 ms    70 ms    71 ms []
22    70 ms    91 ms    83 ms []
23 ...

Also when I ping I get this:
Pinging [] with 32 bytes of data:
Reply from TTL expired in transit.

What could cause this? If DNS is in fact returning, then the route from my network to the server should be the same no matter what domain I query to get the IP!?
I do not manage the DNS for this domain, so that limits testing options.
Question by:LogicLoader
    LVL 3

    Accepted Solution

    IP you are getting for is different than the one you used for the original trace.  The second octet is different.

    Your DNS server has a bad record.

    LVL 3

    Expert Comment

    Oh, the third is different too... somebody made a typo!
    LVL 9

    Expert Comment

    by:jabiii =
    forward and reverse lookups don't match.

    >Also when I ping I get this:
    >Pinging [] with 32 bytes of data:
    >Reply from TTL expired in transit.
    Is normal if there is a FW inbetween you.

    Could be a routing problem, or DNS problem, somoenoe else advertising the

    Don't trace to a DNS name, do a nslookup on the domain, and trace to that IP see if you still get the same symptoms.
    LVL 3

    Expert Comment

    The external DNS servers that are authoritative for the are listing as the IP for  That IP is not the same as what you trace to when tracing to your website names or to

    The autoritative DNS servers for are:  internet address =  internet address =

    Those are the folks to contact.  Tell them to switch the 2nd and third octets in their A record for

    The TTL expired message is just because of the routing loop.

    Author Comment

    Holy !@#$
    Had a lot going on yesterday. I didn't even notice that. I'm so used to seeing the IP, that at a glance those IPs looked the same.

    The routing loop was a red herring, so I didn't even notice.


    Featured Post

    IT, Stop Being Called Into Every Meeting

    Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

    Join & Write a Comment

    Suggested Solutions

    Don’t let your business fall victim to the coming apocalypse – use our Survival Guide for the Fax Apocalypse to identify the risks and signs of zombie fax activities at your business.
    Join Greg Farro and Ethan Banks from Packet Pushers ( and Greg Ross from Paessler ( for a discussion about smart network …
    After creating this article (, I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
    This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor ( If you're looking for how to monitor bandwidth using netflow or packet s…

    745 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    16 Experts available now in Live!

    Get 1:1 Help Now