Hostmastering Working Group:OpenNIC Wiki

Revision [1327]

This is an old revision of HostmasteringWG made by ChrisPugh on 2008-05-23 11:31:38.

Hostmastering Working Group

Coordinators
JulianDemarchi (ns0,ns21,ns22 - .free .geek)

Members
Jeff (Shdwdrgn) (ns2 - ? ? )
JonHebb (ns1 - .null)
ChrisPugh ( ns3, ns4 - .bbs, .fur, .indy, .parody )

Tier1 Master Pool (formerly Tier-1) DNS Hosts

see Tier1Status
and ZoneStatus

Tier2 Public Access (formerly Tier-2) DNS Hosts

SponsoredTLDs Sponsored TLDs

bbs -- dotBbsTLD docs -- dotBbsStatus status ( required) -- links ( required )
free -- dotFreeTLD docs -- dotFreeStatus status -- links
fur -- dotFurTLD docs -- dotFurStatus status -- links
geek -- dotGeekTLD docs -- dotGeekStatus status -- links
indy -- dotIndyTLD docs -- dotIndyStatus status (required) -- links (required)
null -- dotNullTLD docs -- dotNullStatus status -- links
oss -- dotOssTLD docs -- dotOssStatus status -- links
parody -- dotParodyTLD docs -- dotParodyStatus status -- links

The Hostmastering Working Group administers the DNS services and manages the zone files for the RootZone root and GlueZone opennic.glue zones, in accordance with its HostmasteringPolicies Policies

Specifications

DnsSpec DNS Architecture and Configuration

Task List

Deliberate [potential] uses of GlueZone the Glue Zone tree
Implement email lists for each of the t1 and published t2 servers, fed by Nagios.
Make a general whois server available for the TLD operators to use.

Deliberations

PHP form that mails new T2 servers to the technical mailing list for evaluation, if the T2 is setup correctly and a member of the mailing list verifies this, the T2 submission will then be forwarded to the announce mailing list for public notification. (Maybe a WIKI page can be setup for each server verifying the original results of the tests)

The use of the word 'Tier' in naming groups of DNS Hosts is proving inconvenient, even counter-productive, to promoting an understanding of the different functions of these servers. We're looking for, thinking about, and trying out, new lables to replace these, starting with

tier-0 replaced with Aggregate Master, because that's exactly what it is, the DNS "master" for the AggregateRoot;
tier-1 replaced with Master Pool, because that's exactly what it is, a pool of "masters" for the TLDs/zones sponsored by OpenNIC;
tier-2 replaced with Public Access, because that's exactly what they are, public access servers.

We welcome your suggestions and feedback.

I would suggest keeping the tier designations for legacy reasons...many have been involved with OpenNIC over the years, and we would hope they would return to the fold without having to immediately learn a completely new set of nameserver naming rules. The new names are fine, but let's not rush to completely erase the "former" OpenNIC culture! --Brian

Resources

1033: Domain Administrators Operations Guide
1034: Domain Names - Concepts and Facilities
1035: Domain Names - Implementation and Specification
1912: Common DNS Operational and Configuration Errors
1996: A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY)
2136: Dynamic Updates in the Domain Name System (DNS UPDATE)
2308: Negative Caching of DNS Queries (DNS NCACHE)
2541: DNS Security Operational Considerations
2826: IAB Technical Comment on the Unique DNS Root
2870: Root Name Server Operational Requirements
4641: DNSSEC Operational Practices

CategoryHostmastering

OpenNIC Wiki : HostmasteringWG

Revision [1327]