Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] Blending / merging colliding TLDs

discuss AT

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] Blending / merging colliding TLDs

Chronological Thread 
  • From: "Daniel Quintiliani" <danq AT>
  • To: "discuss" <discuss AT>
  • Subject: Re: [opennic-discuss] Blending / merging colliding TLDs
  • Date: Mon, 20 Aug 2018 16:13:32 -0400 (EDT)

This was discussed over the .ing domain we used to have, some of us suggested
to contact the EFF, but the TLD maintainer just shut it down because he
didn't care.

I seem to remember a while ago someone trying to fork OpenNIC, can't remember
who or what name, but the TLD would be anything on request, without the TLD
needing to exist or have a charter (e.g. abcdefg.hijklmn could be registered,
but .hijklmn would not need to exist). I remember it was supposed to override
the gTLDs, but I'm not sure if people were able to "register" ""
for the other users. There were only a few servers, and then it disappeared
after a short time.


-Dan Q

On Mon, 20 Aug 2018 07:58:10 -0500, kevin <krattai AT> wrote:

> I can't remember if this has been discussed at some point in time.
> I'm still a little pissed that we gave up .free to ICANN as though
> ICANN is theĀ Eminent domain gate keeper, though most concede it is.
> While there are many creative ways to name a TLD to be unique and still
> hold meaning, I'm sure there will be many times where a popular term
> may become a TLD on some DNS server and there is a possibility that
> domains may collide in peering arrangements.
> I have some ideas about how to deal (automagically) with colliding
> domains by way of some blending or merging methodology (such as a
> repository of servers handling the TLD and concatenating a list of pre-
> existing domains on that TLD), but would like to hear if anyone else
> has considered this in the past and their method of resolving such a
> possibility.
> Cheers,
> Kevin
> --------
> You are a member of the OpenNIC Discuss list.
> You may unsubscribe by emailing discuss-unsubscribe AT

Archive powered by MHonArc 2.6.19.

Top of Page