<p dir="ltr">We tend to forget the fugly ones :-)</p>
<p dir="ltr">Matt</p>
<div class="gmail_quote">On Jan 21, 2017 1:06 AM, "Bradley D. Thornton" <<a href="mailto:Bradley@northtech.us">Bradley@northtech.us</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="m_-7941443515158753944moz-cite-prefix">On 12/3/2016 9:44 AM, Brian Koontz
wrote:<br>
</div>
<blockquote type="cite">
<p dir="ltr">This is correct. OpenNIC incorporates the ICANN root
into its own root files. .free is a recent collider; we haven't
decided what we're going to do at this point. At any rate, OP
will have to use OpenNIC servers to resolve.</p>
</blockquote>
<br>
When I still provided The PacificRoot as a forward facing public
service, as well as providing the zone data for several other
competing Inclusive Roots at the time, we developed a couple of
different plugins for the OS which, in once case, was merely a .reg
file for wYNd0z3 OSes that adjusted the DNS servers in the system
resolver to use nameservers resolving the Inclusive Name Space.<br>
<br>
With a little .shtml and cgi magic, once the colliding .biz TLD was
introduced by neulevel and ICANN (the antichrist), A query to the
the namespace within .biz would, at the DNS provider level, offer up
a web page requesting the surfer to decide which of the two
colliding .biz TLDS (the original, managed by ARNI, or the
pretender, championed by ICANN) they wanted to resolve in the name
space.<br>
<br>
It worked fine, but you couldn't switch without some effort. We were
working on merging all of the non-colliding SLDs within those two
name spaces when we decided to defer to the antichrist, and remove
the original .biz TLD from the root.<br>
<br>
I've been a charter member of OpenNIC since before Bill Clinton was
marinating cigars. BTW, whatever happened to Robin Bandy?<br>
<br>
<blockquote type="cite">
<p dir="ltr">That's the point of OpenNIC: It's an alternative to
ICANN. </p>
<div class="gmail_quote">On Dec 3, 2016 8:59 AM, "Kacper Gutowski"
<<a href="mailto:mwgamera@gmail.com" target="_blank">mwgamera@gmail.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 3
December 2016 at 08:35, James Mills <<a href="mailto:prologic@shortcircuit.net.au" target="_blank">prologic@shortcircuit.net.au</a>>
wrote:<br>
> I tired to reach this URI from OpenNIC dns servers but
also ran into<br>
> trouble.<br>
> I run a custom dns servers locally and I'm not completely
sure why I kept<br>
> running in to:<br>
><br>
> $ host reg.for.free<br>
> reg.for.free has address 127.0.53.53<br>
> reg.for.free mail is handled by 10
your-dns-needs-immediate-atten<wbr>tion.free.<br>
<br>
Whatever you do, this is the usual result you would get using
the regular<br>
ICANN DNS, not from OpenNIC. The thing is that "free" is a
valid gTLD<br>
and some of those new gTLDs decided never to give NXDOMAIN for
second<br>
level domains and resolve into the above instead.<br>
<br>
$ host -t txt reg.for.free<br>
reg.for.free descriptive text "Your DNS configuration needs
immediate<br>
attention see <a href="https://icann.org/namecollision" rel="noreferrer" target="_blank">https://icann.org/namecollisio<wbr>n</a>"<br>
<br>
$ host reg.for.free $(curl -s<br>
'<a href="https://api.opennicproject.org/geoip/?bare&res=1" rel="noreferrer" target="_blank">https://api.opennicproject.or<wbr>g/geoip/?bare&res=1</a>')<br>
Using domain server:<br>
Name: 96.90.175.167<br>
Address: 96.90.175.167#53<br>
Aliases:<br>
<br>
reg.for.free has address 173.160.58.202<br>
reg.for.free has IPv6 address 2001:470:f032:1::254<br>
<br>
<br>
-k<br>
<br>
______________________________<wbr>_________________<br>
Gopher-Project mailing list<br>
<a href="mailto:Gopher-Project@lists.alioth.debian.org" target="_blank">Gopher-Project@lists.alioth.de<wbr>bian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project" rel="noreferrer" target="_blank">http://lists.alioth.debian.org<wbr>/cgi-bin/mailman/listinfo/goph<wbr>er-project</a><br>
</blockquote>
</div>
<br>
<fieldset class="m_-7941443515158753944mimeAttachmentHeader"></fieldset>
<br>
<pre>______________________________<wbr>_________________
Gopher-Project mailing list
<a class="m_-7941443515158753944moz-txt-link-abbreviated" href="mailto:Gopher-Project@lists.alioth.debian.org" target="_blank">Gopher-Project@lists.alioth.<wbr>debian.org</a>
<a class="m_-7941443515158753944moz-txt-link-freetext" href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project" target="_blank">http://lists.alioth.debian.<wbr>org/cgi-bin/mailman/listinfo/<wbr>gopher-project</a></pre>
</blockquote>
<br>
<br><br>
<hr style="border:none;color:#909090;background-color:#b0b0b0;height:1px;width:99%">
<table style="border-collapse:collapse;border:none">
<tr>
<td style="border:none;padding:0px 15px 0px 8px">
<a href="https://www.avast.com/antivirus" target="_blank">
<img border="0" src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo">
</a>
</td>
<td>
<p style="color:#3d4d5a;font-family:"Calibri","Verdana","Arial","Helvetica";font-size:12pt">
This email has been checked for viruses by Avast antivirus software.
<br><a href="https://www.avast.com/antivirus" target="_blank">www.avast.com</a>
</p>
</td>
</tr>
</table>
<br>
</div>
<br>______________________________<wbr>_________________<br>
Gopher-Project mailing list<br>
<a href="mailto:Gopher-Project@lists.alioth.debian.org">Gopher-Project@lists.alioth.<wbr>debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project" rel="noreferrer" target="_blank">http://lists.alioth.debian.<wbr>org/cgi-bin/mailman/listinfo/<wbr>gopher-project</a><br></blockquote></div>