ADNR not updating zones in a DNS server
Use the following information to determine why changes
to host names are not being updated in the DNS server zone being managed
by ADNR:
- Verify that ADNR is running. If it is not running then start ADNR.
- If message EZD1278E or EZD1257I has been issued, see Diagnosing unresponsive zones.
- Issue display commands with the ADNR MODIFY command to determine
whether it is connected to the GWM and has registered its group and
member data. If not using AT-TLS, verify that the z/OS® Load Balancing Advisor's lb_id_list value
includes the IP address of ADNR specified with the host_connection_addr
keyword of the gwm statement.
If using AT-TLS with SERVAUTH access control checks to validate connections between the Advisor and ADNR, see Diagnosing Application Transparent Transport Layer Security (AT-TLS). In addition, ensure that the SERVAUTH class is active. Ensure that the EZB.LBA.LBACCESS.sysname.tcpsysplexgroupname resource profile is defined and that the load balancer and ADNR have READ access to it. On the system console where the Advisor is running, look for message EZD1280I which indicates that a connection attempt using AT-TLS failed. This message has specific reason codes which indicate the reason for the failure.
- Check the log file for any ADNR ERROR or WARNING messages and take the appropriate corrective action. If ERROR and WARNING level log messages are not enabled, then enable them and recheck the log file later. For more information about the ADNR display commands see z/OS Communications Server: IP System Administrator's Commands.
- Ensure that the ADNR configuration is not changed when ADNR is not active. Removing a dns statement or zone parameter while ADNR is not active causes ADNR to lose control of the information in that name server's zones. The information in this case is considered to be orphaned.