AFPUB-2017-DNS-001-DRAFT-01

This periodic checking should be automated. The checks should be relatively frequent, but not so frequent as to cause any operational impact to either AFRINIC systems or the global DNS. If a nameserver fails a check for the first time, this is initially just recorded. Only after failing multiple lameness checks, should a nameserver be flagged for further action.

10.7 Removal of ‘Lame’ Delegations Once a given ‘nserver’ attribute has been determined to be lame for a given domain, and reasonable attempts have been made to contact the responsible person(s), the nserver attribute must then be removed from the given domain object.

All of the "admin-c", "tech-c" and "zone-c" contacts should be tried in parallel. In addition, contact information may be extracted from associated "org" and/or "mnt-by" attributes when appropriate. Unanswered notification communications should also be re-tried more than once before moving on to further actions. The communication frequency, communication method(s) and number of attempts should be standardised and publicly documented.

Once a given ‘nserver’ attribute has been determined to be lame for a given domain, and reasonable attempts have been made to contact the responsible person(s), the nserver attribute must then be removed from the given domain object.

An optional "remarks" line may be added to the "domain" record in the database. Should a given domain have all it's nameserver's identified as lame, and thus removed, it must then also be removed from the database, due to the "nserver" attribute being mandatory for "domain" objects. Historical information about removed nameservers and domain objects should be archived for a reasonable amount of time and made available to the member for informational purpose.

A ‘remarks’ line should be added to the domain object in the database recording this. In the event all nameserver records are lame for a given delegation, the domain object would be removed in its entirety. Historical information about removed domain objects should be archived for a reasonable amount of time and made available as necessary.

10.7.4 Re-instatement Once nameservers are fixed, or alternate nameservers are available for a given reverse DNS zone, the responsible person(s) would add delegation to them in the same way as a new delegation is done for a new IP assignment or allocation.

3.2 Sample Implementation Guideline A sample operational manual is available online as a suggested guideline to AFRINIC staff. Please note that this is a sample by the authors for a suggested implementation, and not part of the policy. It does not necessarily reflect a final implementation by AFRINIC staff.