Updates to an ADNR-managed zone

Typically, zones managed by ADNR should not be updated by any entity other than ADNR. This includes manual editing of the zone data file, or dynamic updates from any other source. Many name server implementations strongly advise against manually editing the zone data file of a dynamic zone, such as the zones managed by ADNR. Editing these files has the potential to corrupt the file, or the updates can be lost. However, in general from a name server perspective, dynamic updates using a tool such as nsupdate are allowed for dynamic zones. In the case of ADNR-managed zones, certain types of dynamic updates can be made by entities other than ADNR. Table 1 shows which types of resource records can be dynamically added and deleted by entities other than ADNR.

Table 1. Dynamic updates of ADNR-managed zones by other entities
Allowed dynamic updates	Disallowed dynamic updates
All resource record types other than A and AAAA	A and AAAA resource records that are not considered glue records
A and AAAA resource record types that are considered glue records
Tip: Glue records are A or AAAA records that store the IP addresses of authoritative name servers.

Any disallowed resource records that appear in dynamic update requests to ADNR-managed zones are accepted by the name server, but are subject to being deleted by ADNR at a later time.

Rule: ADNR uses a special domain name for determining whether a name server is active and configured correctly to allow dynamic updates. At times, ADNR dynamically performs an update-add and an update-delete of the following resource record:

ibmsaspddnsdnsprobe IN A 0.0.0.0

In the unlikely event that this same resource record is added to an ADNR-managed zone by an entity other than ADNR, it is subject to being deleted by ADNR in the future.