[23875] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: Severe Response Degradation

daemon@ATHENA.MIT.EDU (Derek Balling)
Wed Apr 28 09:21:59 1999

Date: Wed, 28 Apr 1999 06:18:10 -0700
To: Derrick Bennett <Derrick@anei.COM>,
	"'nanog@merit.edu'" <nanog@merit.edu>
From: Derek Balling <dredd@megacity.org>
In-Reply-To: <610B2212FE8BD211815500A0CC39B39C1C00@PROD>
Errors-To: owner-nanog-outgoing@merit.edu



>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


home help back first fref pref prev next nref lref last post