[23885] in North American Network Operators' Group
RE: Severe Response Degradation
daemon@ATHENA.MIT.EDU (Roeland M.J. Meyer)
Wed Apr 28 12:58:17 1999
Reply-To: <rmeyer@mhsc.com>
From: "Roeland M.J. Meyer" <rmeyer@mhsc.com>
To: "Derek Balling" <dredd@megacity.org>,
"Derrick Bennett" <Derrick@anei.COM>, <nanog@merit.edu>
Date: Wed, 28 Apr 1999 09:43:57 -0700
In-Reply-To: <4.2.0.32.19990428061634.009e55e0@mail.megacity.org>
Errors-To: owner-nanog-outgoing@merit.edu
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=20
>=20
>=20
>=20
>=20
> >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=20
> descriptions
> >of locations. I do know that the router is in SF but could not=20
> 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.
>=20
> I haven't actually tried this, but I have been told that if you =
actually=20
> use @Home's DNS servers and query the RFC1918 addresses for the=20
> routers, it=20
> will give you back "intelligent" names.
>=20
> All well and good for average-joe-weenie-@Home-user, but not very=20
> good for=20
> those of us not slaved to their DNS. :)
>=20
> D
>=20
