On Sunday, March 17, 2002, at 06:25 , Simon Byrnand wrote:
At 11:14 18/03/02 +1200, Peter Mott wrote:
Registry may want to have a scheduled task that checks that at least one name server is responding for each zone it delegates. If a particular domain is delegated for for more than x days without an auth answer, then they can remove it from the zone build and notify the registrar who will be required to complete a transaction with the registry to re-include it in the next zone build. This is of course entirely automated :-)
Umm,
Wouldn't it be a bit more polite to notify the technical contact address that they are a lame delegation so that they can have a chance to fix it *before* just removing the delegation ?
I don't think Peter was talking about removing a name from the register due to a lame delegation. He was talking about removing it from the zone file build. The registry should never send mail to the registrant. They should only communicate with the registrars they have contracts with.
Problems can and do occur, and just removing the delegation without some kind of warning isn't very fair.
The registrant gets the same service (no resolution for anything in the zone). Clients trying to resolve names in the zone may get better service, because their recursive lookup attempts fail more quickly in the case that the delegated nameservers do not respond. Joe - To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog