I sent this last week but it seems to have gone to the bit-bucket... Does anyone know of a way to reclaim IPs left registered as hosts by former customers? Let's say Joe Blow moved to another service provider, but he still has ns.joeblow.dom and ns2.joeblow.dom registered using your IP numbers. Netsol gave me this very nice procedure using faxes and followup calls, but I just don't have hours to sit on the phone all day even if my company enjoyed paying the long distance. I would like to see an ISP having equal footing with the domain owner regarding host registrations; that is, the admin contacts and tech contacts OF THE DOMAIN OR OF THE NETBLOCK may delete a host registration. Pros and cons? Or a better forum for this discussion? jcomeau@world.std.com aka John Otis Lene Comeau Home page: http://world.std.com/~jcomeau/ Disclaimer: Don't risk anything of value based on free advice. "Anybody can do the difficult stuff. Call me when it's impossible."
Does anyone know of a way to reclaim IPs left registered as hosts by former customers? Let's say Joe Blow moved to another service provider, but he still has ns.joeblow.dom and ns2.joeblow.dom registered using your IP numbers.
Well, since the domain has no name service, it's clearly dead. My inclination would be to send in an update template with Joe Blow's address in the From: line, documenting in the comments what you're doing. Deleting the domain seems appropriate, but as a lesser measure you could identify new servers 10.255.255.255 and 10.255.255.254 named ns1.lamedelegation.net and ns2.lamedelegation.net. -- John R. Levine, IECC, POB 727, Trumansburg NY 14886 +1 607 387 6869 johnl@iecc.com, Village Trustee and Sewer Commissioner, http://iecc.com/johnl, Member, Provisional board, Coalition Against Unsolicited Commercial E-mail
At 11:57 AM -0400 8/18/00, John R. Levine wrote:
Does anyone know of a way to reclaim IPs left registered as hosts by former customers? Let's say Joe Blow moved to another service provider, but he still has ns.joeblow.dom and ns2.joeblow.dom registered using your IP numbers.
Well, since the domain has no name service, it's clearly dead.
Whoa! That's not (necessarily) what he said is happening. You're reading another sentence in there. He said they moved to another provider, so the new provider MUST be providing service of some kind, how about ... e.g. Where: x.x.x.0/24 is ISP-ONE address-space, y.y.y.0/24 is ISP-TWO address-space. I set up domain.com, at ISP-ONE. I have ns1.domain.com/x.x.x.1, and ns2.domain.com/x.x.x.2. I move domain.com to ISP-TWO and I start using their name servers ns1.isptwo.com/y.y.y.1 and ns2.isptwo.com/y.y.y.2. The domain is NOT lame-delegated, but the address space has been appropriated from ISP-ONE's space In fact, this is a nice DoS in and of itself. Don't like someone? Set up name servers all throughout their address-space, so that they can't use them themselves without jumping through hoops, e.g., ISPONE.COM - x.x.x.0/24 NS1.ISPONESUCKS.COM - x.x.x.1 NS2.ISPONESUCKS.COM - x.x.x.2 ... NS255.ISPONESUCKS.COM - x.x.x.255 What's to stop a belligerent person from doing this? Especially is ISPONESUCKS.COM isn't lame, but maybe has REAL-NS1.ISPONESUCKS.COM - y.y.y.1 REAL-NS2.ISPONESUCKS.COM - y.y.y.2 So you can't easily forge to/from their namespace to delete the errant host declarations, because they can easily NAK the requests. If they're using a registrar with no mail-based forms at all (e.g., OpenSRS), then you can't even try to forge e-mail (since only the Registrar involved with the domain can alter the host-records associated with $DOMAIN) Has anyone seen this DoS in the wild? Strikes me as clinically stupid that nobody has seen this and exploited it in the past... D
On Fri, 18 Aug 2000, Derek J. Balling wrote:
In fact, this is a nice DoS in and of itself. Don't like someone? Set up name servers all throughout their address-space, so that they can't use them themselves without jumping through hoops, e.g.,
...
Has anyone seen this DoS in the wild? Strikes me as clinically stupid that nobody has seen this and exploited it in the past...
This happened to us once with the Argentinian registry. Someone, we know not who, had registered the host ns0.magic-moments.com with them, which we happen to use as the primary NS for domains hosted with us. When we went to register a .ar domain for the first time, our app was rejected because the nameserver record didn't belong to us! Was somewhat of a pain in the arse for our lad to have to sort out. -- Patrick Evans - Sysadmin, bran addict and couch potato pre at pre dot org www.pre.org/pre
participants (4)
-
Derek J. Balling -
John O Comeau -
johnl＠iecc.com -
Patrick Evans