I could be wrong because I don't fully understand BIND internals here,
but if anyone wanted to copy the root domain and add new toplevel domains
like .bork or .die on their own networks, they could just do it. Any
references to .bork or .die would be correctly resolved and any other
references would be delegated to the same .com and .org and .net servers
that are currently in use. If other networks felt there was value in
accessing the .bork and .die domains they would do similarily referencing
your nameserver to resolve such references.
Is there any technical reason this wouldn't work?
Sure. Someone physically DENY'ing you the ability to transfer
zone info or domain lookups. Of course, this is localized
protection, so you could still hijack till your heart's content
on all upper level servers.
DENY'ing is more like a social reason why it won't work. However if there
was value to other hosts in accepting your new domain name *SERVICE* then
it would be used. Without widespread acceptance/cooperation it wouldn't work.
I think this would achieve a number of things. It would let the Internic
off the hook by providing many alternative namespaces, it would reduce
the value of .com domains by making them less exclusive, it would
thoroughly confuse the entire issue of "shortage of good names" and
having the "right domain name". Which is better, cars.com or com.cars or
car.sales or sales.cars or ford.dealer or ford.used or ford.new or
Obviously any company with such a strong trademark that they can prohibit
the use in any context (like Exxon) can still prevail within the
jurisdiction that a give nameserver operates, but most names do not have
such an exclusive control over use and depend heavily on context.
Michael Dillon Voice: +1-604-546-8022
Memra Software Inc. Fax: +1-604-542-4130
http://www.memra.com E-mail: firstname.lastname@example.org