Discuss mailing list

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

Well, yes, but it's going to significantly impact a lot of people trying to use OpenNIC, since Chrome has a massive market share at this point, so it seems like something we should probably at least consider.  If nothing else, we should probably warn users that certain brands of Chrome may malfunction with the DNS because it does not honour resolution properly, IMO.
-mb

On 2016-12-08 04:01, Brian Koontz wrote:

On Wed, Dec 7, 2016 at 9:21 PM, Maiyannah Bishop
<maiyannah.bishop AT postactiv.com> wrote:

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.

This is a browser issue, not an OpenNIC issue.  Google does some
rather unorthodox things (such as redirect to its search engine on
localhost queries that aren't found, or TLDs that aren't recognized).
But this isn't OpenNIC's problem. I'm not so sure we need to be making
policy and what not for browsers that do not resolve correctly.  (BTW,
I see the same thing on Chrome.  I rarely use Chrome given its bad
behavior.)

  --Brian

--------
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