Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

Share this Page URL

Chapter 2: The Resolver > The common design scenarios for the Resolver - Pg. 24

Hard-coded IP addresses Benefits Fast (no name resolution). Good in some debugging situations (you know exactly which IP address is being used). Difficult to remember IP addresses. Very inconvenient in case an IP address change occurs. Just think about IPv6. Local hosts file Fast (local name resolution). Domain Name System (DNS) IP address changes can be done without any local changes. All host names (in the entire network) can be resolved. A hierarchical name space. Additional packets (requests) flow to resolve host name before destination can be reached. Drawbacks If an IP addressing change is needed, all the local hosts files have to be updated. Only locally configured host names can be resolved. 2.3 The common design scenarios for the Resolver When thinking about how to implement the Resolver in a z/OS environment, it is important to understand and review the environment variables and their purpose. To demonstrate how this is done, we are going to show two basic scenarios: Using the Resolver address space in a single stack environment, where we are going to design a Resolver address space with specific global settings and a default Resolver config, and how it applies to a single stack environment. Using the Resolver address space in a multiple stack environment, setting up a Resolver