Hello, I ended up e-mailing reseller support, as was suggested.
--- John Peacock <[EMAIL PROTECTED]> wrote: > George Kirikos wrote: > > I acquired a domain name that had some nameservers defined for it, > that > > are being used by some other domains. > > So what. You are fully capable of taking that nameserver offline > (incapable of responding to queries) or just create wildcard records > for > those foreign domains that will kill their nameservices. It should > be > trivial to force someone to change their nameserver record by being > nasty, so it should be easy to convince them to reconfigure their > domains by being nice. In this age of DDoS attacks (e.g. Blue Security), one wants to be careful to play nice, and not be nasty. Having the name move into a "lame delegation" nameserver (perhaps via some under-reported registry command?) is better practice than taking control of the domain oneself, esp. given the potential legal liability of answering for someone else's domain. > > I don't want to point it to a routable IP address, lest someone > hijack > > the other domains. > > I don't understand this concern, however. *You* control the > nameserver > and what records it serves up. No one can hijack anything since you > are > the one in control of the IP address. *You* can hijack (at least > partially, see below) the other domains, but no one else can (unless > they control one of the other nameservers for those domains). Right, I don't want to be in a position to be accused of hijacking other people's domain -- I play nice. :) Pointing it to a random routable address is not good either, since someone else can later put up a nameserver at that IP address. Sincerely, George Kirikos http://www.kirikos.com/ _______________________________________________ domains-gen mailing list [email protected] http://discuss.tucows.com/mailman/listinfo/domains-gen
