Revision [957]
This is an old revision of HostmasteringWG made by AvoYager on 2007-09-24 16:05:58.
Coordinators Robin (ns0), AvoYager (ns20)
Members
Jeff (Shdwdrgn) (ns2 - .oss .parody)
JulianDemarchi (ns21 - .free)
Tier1 Master Pool (formerly Tier-1) DNS Hosts
Tier2 Public Access (formerly Tier-2) DNS Hosts
SponsoredTLDs Sponsored TLDs
Members
Jeff (Shdwdrgn) (ns2 - .oss .parody)
JulianDemarchi (ns21 - .free)
Tier1 Master Pool (formerly Tier-1) DNS Hosts
Tier2 Public Access (formerly Tier-2) DNS Hosts
SponsoredTLDs Sponsored TLDs
free -- dotFreeTLD docs -- dotFreeStatus status -- links
geek -- dotGeekTLD docs -- dotGeekStatus status -- links
parody -- dotParodyTLD docs -- dotParodyStatus status -- links
geek -- dotGeekTLD docs -- dotGeekStatus 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
Task List
- Integrate VolunteerHosts Volunteering Hosts
- Deliberate [potential] uses of GlueZone the Glue Zone tree
Deliberations
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.
- 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
- http://www.bind9.net/rfc
- http://www.bind9.net/dnshealth
- Domain Administrators Operations Guide
- Common DNS Operational and Configuration Errors
- A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY)
- Dynamic Updates in the Domain Name System (DNS UPDATE)
- DNS Security Operational Considerations
- IAB Technical Comment on the Unique DNS Root
- DNSSEC Operational Practices
CategoryHostmastering
