Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] Important: reg.for.free, and thus .geek and .indy signups unavailable

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] Important: reg.for.free, and thus .geek and .indy signups unavailable


Chronological Thread 
  • From: Jonah Aragon <jonaharagon AT gmail.com>
  • To: discuss <discuss AT lists.opennicproject.org>
  • Subject: Re: [opennic-discuss] Important: reg.for.free, and thus .geek and .indy signups unavailable
  • Date: Mon, 12 Dec 2016 08:38:20 -0600

He's referring to the ICANN Collision error in Chrome that happens if you access a domain that exists both on your local DNS and as an ICANN resolvable domain, not the weird Chrome behavior that searches instead of resolves custom domains. 

See reports people posted about .dev when that became a TLD, for example: http://stackoverflow.com/questions/31216990/icann-name-collision-chrome

Or look at the Chrome design spec for that specific error page: https://docs.google.com/document/d/123BYF7vcgAPq5oTiwuhKJfRNMTPmOFgofl2ZkQHOBqY/edit?usp=sharing

It's a useless error, and yet another example of how Chrome completely messes up projects like ours. But it's definitely a Chrome bug, not user error. 

Jonah

On Dec 12, 2016 7:57 AM, "Jeff Taylor" <shdwdrgn AT sourpuss.net> wrote:
Chrome has always been broken with respect to handling custom local TLDs, UNLESS you remember to include the trailing slash -- for example, http://reg.for.free/

So is it broken now when you include the trailing slash for opennic domains?

And yes, if you're seeing the page with the list of domains, that's just my default landing page.

OpenNic doesn't have a .reg TLD, so registering.reg and openinc.reg of course would not work.  Not sure why this was listed as a problem.



On 12/09/2016 02:10 PM, Maiyannah Bishop wrote:
Yeah, it doesn't seem a gamebreaker or anything, but does seem worth noting.

The reg.for.free ones "just" have the silly Chrome behaviour which for now seems to have sufficiently been banished by a hosts file override.  register.fur seems straight up down though, and isn't on reg.for.free, now that I look

-mb

On 2016-12-09 16:06, Jonah Aragon wrote:
I think the gopher registration page is being reworked, last I heard. But you can register them at reg.for.free so it doesn't matter that much overall. I don't know about other domains. Which ones are having issues besides .gopher?

Jeff (Shdwdrgn) manages a lot of TLDs nowadays (look at the list ns2 has on the servers page) so a lot of them might also have reg.for.free options if their individual sites are down.

Jonah





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





Archive powered by MHonArc 2.6.19.

Top of Page