Discuss mailing list

[Maiyannah Bishop <maiyannah.bishop AT postactiv.com>]

Just for a little further information, if you visit reg.for.free now without OpenNIC, it gives "ERR_ICANN_NAME_COLLISION" in Chrome, irrespective of version.
With OpenNic in Firefox it seems to with, but this branch of Chrome returns the name collision error with or without OpenNIC resolution, so it seems that there's a change in that behaviour, probably to favour ICANN.

It doesn't really give me more diagnostic information than that though.

I tried with a few OpenNIC DNS servers just to be sure it wasn't some sort of malfunction of the ones I was using at the moment.
-mb

On 2016-12-07 23:16, Maiyannah Bishop wrote:

I use a dev branch of Chrome so it's probably specific to some upcoming "feature" (like their one in 53 one that broke literally half the internet with certificate problems...) but it does seem to work in Firefox, so I guess I'll use that for now.  It's definitely a looming problem if this is something I'm running into on a dev branch though.
-mb

On 2016-12-07 23:11, Jonah Aragon wrote:

Still working for me in Chrome and Edge, definitely a browser specific issue, so if it doesn't work just try another one. But I agree, it's definitely going to become an issue very shortly, this is why we're working on changing the .free TLD now before this kind of stuff is more widespread.

Jonah

On Dec 7, 2016 10:06 PM, "Maiyannah Bishop" <maiyannah.bishop AT postactiv.com> wrote:

Or rather more specifically, navigating to the page will result in errors in most web browsers because of the name collision with the ICANN domain.  Irrespective of what we plan to do with .free as a TLD, we should get a page working as an alternative for registrations.  As is, because the registration is on this domain, .indy and .geek registrations are also unavailable, and I do not believe these gTLDs.  I guess I'll just have to go with the .com I managed to snag for the little starter homepage I was knocking up for my name server.

To the best of my knowledge, the .indy TLD at least isn't contested, and my existing domain seems to resolve fine, but I cannot register a new one as a result of this, which I was hoping to do as a domain name by which a little "howto" frontpage for the nameserver could be reached.
-mb

--------
You are a member of the OpenNIC Discuss list. 
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org

Attachment: signature.asc
Description: OpenPGP digital signature