Skip to Content.
Sympa Menu

discuss - [opennic-discuss] Some new ICANN links for OpenNIC content

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

[opennic-discuss] Some new ICANN links for OpenNIC content


Chronological Thread 
  • From: Jeff Taylor <shdwdrgn AT sourpuss.net>
  • To: OpenNIC DNS Discuss <discuss AT lists.opennicproject.org>
  • Subject: [opennic-discuss] Some new ICANN links for OpenNIC content
  • Date: Tue, 17 Feb 2015 12:04:09 -0700
  • Authentication-results: mx2.sourpuss.net; dmarc=none header.from=sourpuss.net
  • Dmarc-filter: OpenDMARC Filter v1.3.0 mx2.sourpuss.net 739D32D41A

We have purchased a couple new ICANN domains to help ease the access to OpenNIC pages and possibly get some traffic coming from the big search engines. While we have a general idea for using these new links, we're open to discussion for new ideas...

http://opennic.pw/
This page is currently redirected to http://www.opennicproject.org/members/. The new link will likely be a lot easier to remember for anyone wishing to visit the member's page. (Yes I know, I still need to ADD password functionality to the member's page, the irony is not lost.)

http://opennic.link/
This one has the most potential for us. The idea is to add DNS records to create subdomains for existing OpenNIC domains. So for example you could go to http://reg.dyn.opennic.link/ and register a new domain. There are a number of pointers already created, however I am running a script to comb through all of our domains to collect anything that was missed in the first pass. Please note that this will only be applied to OpenNIC TLDs, and the .bit domains will NOT be included in this (they are more of a specialized peer, and providing direct ICANN access to their records is likely against their terms).

For those who are interested in having your website available through the ICANN domain, you must add the appropriate info to your webserver configuration. For apache users this would mean adding a ServerAlias directive (IE: ServerAlias reg.dyn.opennic.link). For nginx, add the new name to server_name. I will have a much more accurate zone file for opennic.link sometime later today, which should include A/AAAA records for all active opennic domains.

If anyone wants to discuss including other record types, please state why you want to include it. I could see a reason for adding MX records so that mailservers under opennic domains were reachable through ICANN, but I think this should be done on an individual basis (where the server admin makes a direct request for their record to be added to opennic.link). Any others?



Archive powered by MHonArc 2.6.19.

Top of Page