IP Services: Migrate from BIND 9.2.0
Description
z/OS V1R13 was the last release that supported the z/OS BIND 9.2.0 name server function. If you are using this function as a name server, you must find a replacement.
Table 1 provides more details about this migration action. Use this information to plan your changes to the system.
| Element or feature: | Communications Server |
|---|---|
| When change was introduced: | The removal of the BIND 9.2.0 function was first announced in February 2009. z/OS V1R13 was the last release that supported the z/OS BIND 9.2.0 name server function, as stated in the z/OS V1R13 preview announcement on February 11th, 2011. |
| Applies to migration from: | z/OS V1R13. |
| Timing: | Before installing z/OS V2R2. |
| Is the migration action required? | Yes, if you are using the BIND 9.2.0 function as a name server. |
| Target system hardware requirements: | None. |
| Target system software requirements: | None. |
| Other system (coexistence or fallback) requirements: | None. |
| Restrictions: | None. |
| System impacts: | None. |
| Related IBM Health Checker for z/OS check: | ZOSMIGV1R11_CS_DSNBIND9. |
Steps to take
Follow these steps:
- If you are using z/OS BIND 9.2.0 as a caching-only name server, use the z/OS resolver DNS caching function to cache DNS responses.
- If you are using z/OS BIND 9.2.0 as a primary or secondary authoritative name server, investigate using BIND on Linux for System z.
- Update the NSINTERADDR statements in the resolver configuration file.
- If the z/OS BIND 9.2.0 name server is the only name server to be contacted in the NSINTERADDR list of name servers, replace the name server entry with one or more name server IP addresses.
- If more than one name server is in the NSINTERADDR list of name servers, delete the IP address of the z/OS BIND 9.2.0 name server.
- If the automated domain name registration(ADNR) application is being used, ensure the name server is configured to support ADNR. See z/OS Communications Server: IP Configuration Guide for configuring automated domain name registration.
Reference information
For more information
about the resolver, see the following references: