[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nanog
Subject:    RE: Severe Response Degradation
From:       "Roeland M.J. Meyer" <rmeyer () mhsc ! com>
Date:       1999-04-28 16:43:57
[Download RAW message or body]


I have tried it, and forgotten about it, should have mentioned it. This works. The \
problem is that you need a node to traceroute to first. But y'all already have that \
<grin>.

> -----Original Message-----
> From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of
> Derek Balling
> Sent: Wednesday, April 28, 1999 6:18 AM
> To: Derrick Bennett; 'nanog@merit.edu'
> Subject: RE: Severe Response Degradation 
> 
> 
> 
> 
> > This is what we are currently seeing. Unfortunately @Home does not do
> > reverse dns for their routers so I am going by their helpdesk's 
> descriptions
> > of locations. I do know that the router is in SF but could not 
> get an exact
> > location due to @home claiming it to be a sprint issue. This also brings
> > back the conversation of RFC1918 addressing and the problems it can cause
> > when troubleshooting response issues.
> 
> I haven't actually tried this, but I have been told that if you actually 
> use @Home's DNS servers and query the RFC1918 addresses for the 
> routers, it 
> will give you back "intelligent" names.
> 
> All well and good for average-joe-weenie-@Home-user, but not very 
> good for 
> those of us not slaved to their DNS. :)
> 
> D
> 


[prev in list] [next in list] [prev in thread] [next in thread]