Registering domains behind the nameserver ops' backs.

Jay R. Ashworth jra at scfn.thpl.lib.fl.us
Mon Jul 14 19:18:50 UTC 1997


On Mon, Jul 14, 1997 at 02:11:55PM -0400, Robert A. Pickering Jr. wrote:
> What if I registered a domain against your nameservers and then
> advertised it?  What would your nameservers do with the lame delegations?
> I've had lame delegations really mess up my DNS servers.  They spend all
> their time asking the top-level servers, who just point back to them.

I had a related problem just recently.

tsp.net is about to move.  baylink.com and tbtoday.com (among others)
will be taking over the physical hardware, servers, and network
numbers.

So I tried to submit host registrations for ns1. and ns2.baylink.com.

One went through fine, the other disappeared.  The _reason_ it
disappeared was that the IP address already was registered... as
tsp-hst (tsp.net).

Hold on, cause this is where it gets pertinent.

I had to call and have the domain reg for tbtoday.com hand walked.
They ran it through... wih tsp.net as one of the nameservers.  They
didn't confirm it, although they did carbon the registration approval
to the registered contact for that nameserver.

So, what _is_ their policy supposed to be here?

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra at baylink.com
Member of the Technical Staff             Unsolicited Commercial Emailers Sued
The Suncoast Freenet      "People propose, science studies, technology
Tampa Bay, Florida          conforms."  -- Dr. Don Norman      +1 813 790 7592



More information about the NANOG mailing list