We do the same thing (ns-not-in-service.com)....
If a domain expires, we delete it (at the end of the process).
If the domain has a nameserver, we cannot delete the domain.
We delete the nameserver, then the domain
If the nameserver is being used by other domains, we cannot delete it.
We rename the nameserver, so we can delete its host domain
It's a necessity, or we eat the autorenewal cost.
This case may have been different (but I'm not sure), since I DO know that
Verisign Registry has been doing considerable work to delete "orphaned" A
records (if an OpenSRS domain you sponsor was affected, you'd have been
notified - this process is long over)
Charles Daminato
OpenSRS Product Manager
Tucows Inc. - [EMAIL PROTECTED]
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED]
> Sent: August 9, 2002 12:51 AM
> To: Michael-Pappas
> Cc: [EMAIL PROTECTED]
> Subject: Re: Changes to name server records..
>
>
> On Fri, 9 Aug 2002, Michael-Pappas wrote:
>
> > Still, the domain name was not working when this change occoured, only
> > when we delegated the domain name back to the hosts server
> details did the
> > site come back up online...
>
> There must have been a nameserver in the list which was passing out the
> bad data. That would have happened irrespective of Verisign renaming
> those records; I doubt there's a connection between the two events.
>
> > Also it really does not make sence that they had to change the names of
> > the servers but not the IP addresses... why not remove the records
> > completly... what good is changeing the name and not the IP...??
>
> Removing the records entirely would have caused any domain names which
> were still using those records to stop working. Technically, the registry
> can't delete nameserver records until they are no longer attached to any
> domains, and detaching them would have potentially left many domains
> without any nameservers.
>
> --
> Alex Bulan <[EMAIL PROTECTED]>
> Korax Inc.
>