Discuss mailing list

[Martin C <martin AT mchomenet.com>]

Ok, the latest updates for MUD4TLD went up this morning, and while I'm 
checking how it goes under real world conditions versus my home test 
server, I'm thinking about the next step. This is because MUD4TLD, 
unless something else comes up, is essentially 90-95% feature complete 
for what it was designed to do.

Among the many items on my wishlist, I think I need a slightly easier 
task rather than a hugely complex one for a break. So I have decided to 
have a look at implementing the Remote Management API.

Now, before going ahead with it, I will do two things, first is to 
describe it:
* Remote Management API means that while TLD managers do just that, 
manage TLDs, a remote management API allows others who run DNS 
management systems to remotely register and delete domains as well as 
host DNS.

An example of this could be: TLD managers would be like, eg: Verisign 
and DNS providers like ZoneEdit, Dyn, freedns.afraid.org, etc (plus 
OpenNIC members who wish to provide similar services once my DNS manager 
is implemented) would also be able to act as registrars, registering 
domains in the various OpenNIC TLDs for their users. Well, OpenNIC TLDs 
running the MUD4TLD suite anyway.

Of course, perhaps some OpenNIC TLD managers might like to offer DNS 
services direct, such as record management, group ownership of a domain, 
dynamic DNS updates, etc. This is fine and will be supported once the 
DNS manager module is complete.

But for now, and secondly to the point above, is there a demand among 
the OpenNIC community for this? or do we want to strictly have domain 
registrations only come through opennic.TLD/register.TLD?

Otherwise, I'll keep working on improving the WHOIS server to be able to 
run from a central point in the OpenNIC network and be able to 
transparently re-direct a WHOIS query to the appropriate MUD4TLD running 
TLD server to extract the information that it needs.

Martin.