nslookup 205.137.63.106
Name: pcslink.phoenix.agis.net
Address: 205.137.63.106
nslookup 206.43.160.160
Name: rt01.pcslink.com
Address: 206.43.160.160
NT Trace, #2 is IRX (rt01)
[d:\users\ryan]tracert www.agis.net
Tracing route to webserver.agis.net [205.137.48.130]
over a maximum of 30 hops:
1 10 ms <10 ms <10 ms acheron.pcslink.com [206.43.161.33]
2 * * * Request timed out.
3 10 ms 10 ms <10 ms agis-pcslink.phoenix.agis.net [205.137.63.105]
4 291 ms 100 ms 70 ms h1-0.952.losangeles1.agis.net [206.185.157.250]
5 270 ms 260 ms 241 ms h1-0.45.detroit1.agis.net [205.137.60.245]
6 360 ms 211 ms 270 ms s1.dearborn1.agis.net [205.137.60.114]
Unix Trace, #1 is IRX (rt01)
pcslink.com$ traceroute www.agis.net
traceroute to webserver.agis.net (205.137.48.130), 30 hops max, 40 byte packets
1 rt01.pcslink.com (206.43.160.160) 1.347 ms 1.09 ms 1.098 ms
2 agis-pcslink.phoenix.agis.net (205.137.63.105) 3.876 ms 3.598 ms 3.977 ms
3 h1-0.952.losangeles1.agis.net (206.185.157.250) 308.684 ms 474.887 ms 502.649 ms
4 h1-0.45.detroit1.agis.net (205.137.60.245) 364.199 ms 139.425 ms 158.457 ms
Nope try again... Its NOT a DNS issue. I hate to say your clueless... But
you DID insinuate that I am, I kinda resent that... Especially when I've
actually taken the time to look into the problem.... If I was clueless, well
thats another story :)
I've actually rebooted my PC into un*x & NT and I see two different results,
NT doesn't work un*x does. I'd say that its a fairly clear cut case of
Livingston and M$ not playing together like nice little children in this
particular instance... I personally can't blame either one, because it
only happens when the two meet... NT can see other routers, and other
traceroutes can see livingston... where oh where to point the finger...
<sarcasm>
I actually looked for an example, with no reverse, but couldn't find one
reall quick... Its getting harder to look down on people as clueless
idiots for no reverse nowdays... My moral superiority complex is being
hurt.
</sarcasm>
>
> The problem described below is because there is not a reverse entry in the
> ARPA/reverse file for that first 206.129.67.11 address. What traceroute
> tries to do is do a reverse lookup on the IP address so that it can display
> the name. (Notice how all other hops start with the name and not the IP).
> Traceroute tries to do the reverse lookup for about 5 times then if it cant
> do the resolve it gives up. The problem is not with the router! There is
> a command line option for traceroute which turns off the reverse lookup
> feature. Enable that and you will see that all is fine. Or you could put
> an entry in the reverse file for that address and all will be fine.
>
> At 08:44 PM 11/6/96 -0700, you wrote:
> >
> >I saw it from an NT 3.51 workstation machine too... did M$ break
> >something else, or are we just doing something wierd?
> >It's really odd because some other network stat packages (that
> >include traceroute) seem to work fine on the same box... Its just
> >the included NT tracert that wanks.
> >
> >> I've definately seen this as well, from win95 machines (haven't
> >> had chance to test anything else). It's fairly consistant;
> >> we finally gave up trying to figure it out.
> >>
> >> On Wed, 6 Nov 1996, MegaZone wrote:
> >
> >> > Once upon a time Jed Stafford shaped the electrons to say...
> >> > >When we trace route to our servers we get a Request timed out message
> >> > >everytime 1 hop away from our router. Here is a copy of the trace route.
> >> > >
> >> > >Tracing route to ixa.net [199.242.19.1]
> >> > >over a maximum of 30 hops:
> >> > >
> >> > > 1 <10 ms <10 ms <10 ms 206.129.67.11 (<---ROUTER)
> >> > > 2 * * * Request timed out.
> >> > > 3 13 ms 12 ms 12 ms border14-ser-1.sea.IXA.net
> >> > >[204.194.9.105]
> >> > > 4 16 ms 15 ms 22 ms border10-eth-0.sea.IXA.net
> >> > >[199.242.16.60]
> >> > > 5 21 ms 23 ms 20 ms pike-ser-0-T1.sea.IXA.net [204.194.9.62]
> >> > > 6 22 ms 35 ms 21 ms ixa.net [199.242.19.1]
> >> > >
> >> > >Can anyone advise as to what we need to do, or have our ISP do to
> >> > >prevent this from happening. We have a IRX-211.
> >> >
> >> > What type of machine are you tracerouting from?
> >> >
> >> > -MZ
> >> > --
> >> > Livingston Enterprises - Chair, Department of Interstitial Affairs
> >> > Phone: 800-458-9966 510-426-0770 FAX: 510-426-8951 megazone@livingston.com
> >> > For support requests: support@livingston.com <http://www.livingston.com/>
> >> > Snail mail: 6920 Koll Center Parkway #220, Pleasanton, CA 94566
> >> >
> >>
> >>
> >
> >----------------------------------------------------------------------------
> >Ryan Mooney Phone (602)265-9188 PCSLink
> >ryan@pcslink.com Fax (602)265-9357 Internet Services
> >
> >The world needs more bitter, twisted souls. It would be a much better place.
> >-----------------------------------------------------------------------------
> >
>
>
----------------------------------------------------------------------------
Ryan Mooney Phone (602)265-9188 PCSLink
ryan@pcslink.com Fax (602)265-9357 Internet Services
The world needs more bitter, twisted souls. It would be a much better place.
-----------------------------------------------------------------------------