ADNR can manage name servers that support RFC 2136, Dynamic Updates in the Domain Name System (DNS UPDATE). For information about accessing RFCs, see Related protocol specifications.
The name servers that ADNR communicates with can be existing name servers, or name servers you set up exclusively for ADNR. Each name server that ADNR is to communicate with is identified on the dns_id keyword of the dns statement.
You might also want to configure one or more secondary name servers for the ADNR-managed zones. Secondary name servers replicate zone data information from the master name server for those zones. Typically, secondary name servers are configured to avoid a single point of failure if a name server fails, and to reduce network traffic by locating secondary name servers in strategic areas of a network so that name server lookups traverse fewer hops in the network.
ADNR does not communicate directly with secondary name servers. Secondary name servers communicate directly with the master name server by performing zone transfers. Ideally, because of the dynamic nature of the data in the zones that ADNR manages, secondary name servers need to be updated as soon as the master name server is updated by ADNR. Otherwise, the secondary name server contains stale information that does not accurately reflect the current availability of sysplex resources. Some name server implementations can minimize the latency with which secondary name servers are updated from their masters, if they have implemented RFC 1996, A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY). For information about accessing RFCs, see Related protocol specifications.