Discuss mailing list

[Travis Peacock <teamcoltra AT gmail.com>]

As one of those abandoners (I was going through one of my long depressive phases, thanks Jeff for stepping in) maybe I shouldn't get a say here but I do totally agree with what you're addressing. 

Off the top of my head there are two solutions that are not exclusive: 

* Create an OpenNIC SSO service that we encourage T1s to use

* Move to a registrar model and maybe setup a single official registrar as the template if others want to have one that's fine. 

Basically try to centralize contact information and make T1 operation less user focused by default making the system more fail proof for the T1s

Travis McCrea
us: +1(206)552-8728

On Mon, 16 Feb 2026, 07:31 Jeff Taylor, <shdwdrgn AT sourpuss.net> wrote:

 From the previous thread, I believe we should have a discussion about
TLD control.  When opennic gets quiet for a period, we seem to keep
losing TLD admins.  There is also the issue of some TLDs which appear to
still be responding, but nobody can get ahold of the admin to registered
or update domains.

Just to remind everyone, I am the admin of NS2 and run the registrations
for dyn, geek, gopher, indy, libre, oss, parody, pirate.  I wrote my
software with this problem in mind, and all domain information is stored
in LDAP which is mirrored on at least four different servers in various
locations.  If I disappear, the data is preserved for others to pick up,
and the schemas used are available is anyone else want to write their
own registration software.  And yes, there are still bugs in my code.

So the discussion I want to have here is whether anyone else is
concerned about the TLDs with no online registration path?  At the very
least, there is no published record of who registered each domain, so
opennic has no method of rebuilding a TLD if needed.  Is there any
interest in consolidating ALL of the TLDs for registration from a single
location?  The current setup would allow any T1 operator to administer
domains under all of the TLDs.  We've even had the web code running from
other locations in the past.  I just want to put this out as something
to consider, a method to try and make it easier for everyone to maintain
their domains.

On the other hand, Opennic is a *learning* project, so of course many
people want to try running a TLD entirely on their own, which is why
things are set up in the current manner.  We shouldn't discourage
anyone's quest for knowledge.  The question is, which aspects of opennic
should be wide-open, and which aspects should have a little stricter
control?


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