[thelist] FW: SOA RNAME field in NSI Registry-administered zones

[Greg Strange]

Thought I would pass this along to you guys.   <tongue_n_cheek>I don't how
much you guys like NSI</tongue_n_cheek> but this really takes the cake.
This will delay updates to zone records all across the Internet.  In fact as
it stood just a half hour ago (3:00pm CDT) every zone was misconfigured at
the root servers.

.    1D IN SOA A.ROOT-SERVERS.NET. zone\@nsiregistry.NET. (
edu. 23h59m19s IN SOA A.ROOT-SERVERS.NET. zone\@nsiregistry.net.edu. (
com. 23h23m53s IN SOA A.ROOT-SERVERS.NET. zone\@nsiregistry.net.com. (
net. 23h57m54s IN SOA A.ROOT-SERVERS.net. zone\@nsiregistry.net.net. (
org. 1D IN SOA A.ROOT-SERVERS.NET. zone\@nsiregistry.net.org. (
gov. 1D IN SOA A.ROOT-SERVERS.NET. GARY\.BORGOYNE.FED.gov. (

It looks pretty but it doesn't work too well.

Remember distribution can take three days not to mention cache only
nameservers.

Greg Strange
-- 
Gather ye rosebuds while ye may,
Old Time is still a-flying,
And this fair bud that blooms today,
Tomorrow will be dying.

----------
> From: "Larson, Matt" <mlarson at netsol.com>
> Date: Fri, 28 Jul 2000 15:26:47 -0400
> To: nanog at merit.edu, "'bind-users at isc.org'" <bind-users at isc.org>,
> DOMAIN-POLICY at LISTS.INTERNIC.NET
> Subject: SOA RNAME field in NSI Registry-administered zones
> 
> 
> The NSI Registry is always striving to improve the build and distribution
> process for the zones we administer.  On Thursday, a new version of this
> build process went into production.  Unfortunately, the information used to
> produce the SOA RNAME field was incorrect and it slipped through our QA
> process.  We have resolved the issue, and zones with the correct information
> are being distributed.
> 
> Matt Larson <mlarson at netsol.com>
> DNS Platform Manager
> Network Solutions Registry / www.nsiregistry.com
> 
> 
>