Example: DNS and DHCP on different System i models

 

This example explains how to set up Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS) on two different System i™ models to perform dynamic updates over a simple LAN.

The following illustration depicts a small subnet network with DNS and DHCP running on separate System i models. The system running DNS is configured the same as when DNS and DHCP are on the same System i model. However, there are some additional steps to configure the DHCP server to send dynamic updates.

Figure 1. DNS and DHCP on different System i models

 

Planning the DHCP setup when using Dynamic DNS

Refer to Example: DNS and DHCP on the same System i for examples of the global configuration options and subnet settings.

 

Other setup:

Installing i5/OS® Domain Name System (Option 31).

Install i5/OS Domain Name System (Option 31) on the System i model that will be running DHCP, in this case, mysystemi2. This option contains the dynamic update API that manages the resource record update process. Refer to DNS system requirements for installation instructions.

Authorizing DHCP to send updates to DNS

You must authorize the DHCP server to send updates to the DNS server. You can either repeat the process of defining the Dynamic Update Key, or you can send the file and place it in the appropriate directory path.

To create a Dynamic Update Key on both System i models, follow these steps:

  1. In iSeries Navigator, expand your system > Network > Servers > DNS.

  2. In the left pane, right-click DNS and select Manage Dynamic Update Keys.

  3. On the Managing Dynamic Update Keys page, select Add.

  4. On the Add Dynamic Update Keys page, complete the following fields:

    • Key name: Specify the name for the key, for example mycompany.key. The key name must be dot-terminated.

    • Dynamic update zones: Specify the zone names for which this key will be valid. You can specify more than one zone.

    • Generate key: Select the method that you want to use to generate a secret key.

  5. Repeat the preceding steps so that the same key is defined on both the System i model running DNS and the system running DHCP.

 

Parent topic:

Examples: DHCP

Related concepts
Domain Name System requirements

Related information
Update DNS API