137 lines
8.5 KiB
HTML
137 lines
8.5 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="reference" />
|
||
|
|
<meta name="DC.Title" content="Example: DNS and DHCP on the same iSeries server" />
|
||
|
|
<meta name="abstract" content="You can learn how to set up the iSeries server as a DHCP server with dynamic DNS updates for a simple LAN." />
|
||
|
|
<meta name="description" content="You can learn how to set up the iSeries server as a DHCP server with dynamic DNS updates for a simple LAN." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgexampleparent.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgscenario7.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzakgscenario4" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Example: DNS and DHCP on the same iSeries server</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakgscenario4"><a name="rzakgscenario4"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Example: DNS and DHCP on the same iSeries server</h1>
|
||
|
|
<div><p>You can learn how to set up the iSeries™ server as a DHCP server with
|
||
|
|
dynamic DNS updates for a simple LAN.</p>
|
||
|
|
<div class="section"><p><a href="#rzakgscenario4__dynamicdns">Figure 1</a> illustrates how
|
||
|
|
the iSeries server
|
||
|
|
can act as a DHCP and DNS server for a simple subnet. In this work environment,
|
||
|
|
suppose that the inventory, data entry, and executive clients create documents
|
||
|
|
with graphics from the graphics file server. They connect to the graphics
|
||
|
|
file server by a network drive to its host name.</p>
|
||
|
|
<div class="fignone" id="rzakgscenario4__dynamicdns"><a name="rzakgscenario4__dynamicdns"><!-- --></a><span class="figcap">Figure 1. Dynamic DNS and DHCP</span><br /><img src="rzakg507.gif" alt="Dynamic DNS and DHCP." /><br /></div>
|
||
|
|
<p>Previous versions of DHCP and DNS were independent of each other.
|
||
|
|
If DHCP assigned a new IP address to a client, the DNS records had to be manually
|
||
|
|
updated by the administrator. In this example, if the graphics file server's
|
||
|
|
IP address changes because it is assigned by DHCP, then its dependent clients
|
||
|
|
are unable to map a network drive to its host name because the DNS records
|
||
|
|
contain the file server's previous IP address.</p>
|
||
|
|
<p>With the new DNS server
|
||
|
|
delivered in V5R1, you can dynamically update your DNS records in conjunction
|
||
|
|
with intermittent address changes through DHCP. For example, when the graphics
|
||
|
|
file server renews its lease and is assigned an IP address of 10.1.1.250 by
|
||
|
|
the DHCP server, the associated DNS records are updated dynamically. This
|
||
|
|
allows the other clients to query the DNS server for the graphics file server
|
||
|
|
by its host name without interruption.</p>
|
||
|
|
<p>You can configure DHCP to update
|
||
|
|
resource records on address mapping (A) records and reverse-lookup pointer
|
||
|
|
(PTR) records on behalf of a client. The A record maps a client's host name
|
||
|
|
to its IP address. The PTR record maps a client's IP address to its host name.
|
||
|
|
For each record that is updated dynamically, an associated text (TXT) record
|
||
|
|
will be written to identify that the record was written by DHCP. You can choose
|
||
|
|
to allow DHCP to update both A and PTR records, or just PTR records. For more
|
||
|
|
information about how to configure DNS to accept dynamic updates, refer to
|
||
|
|
Example: DNS and DHCP on the same iSeries server in the DNS topic.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> If
|
||
|
|
you set DHCP to update only PTR records, you must configure DNS to allow updates
|
||
|
|
from clients so that each client can update its A record. Not all DHCP clients
|
||
|
|
support making their own A record update requests. Consult the documentation
|
||
|
|
for your client platform before choosing this method.</div>
|
||
|
|
<p>To enable DNS
|
||
|
|
updates, you must create a DNS key for your DHCP server. The DNS key authorizes
|
||
|
|
the DHCP server to update the DNS records based on IP addresses it has distributed.
|
||
|
|
Then, in the DHCP configuration, choose the scope level where you want DNS
|
||
|
|
updates to occur. For example, if you want all subnets to perform DNS updates,
|
||
|
|
set the updates at the Global level. If you want only one subnet to perform
|
||
|
|
updates, then set only that subnet to update.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Planning the DHCP setup when using Dynamic DNS</h4>
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="100%" frame="border" border="1" rules="all"><caption>Table 1. Global configuration options (applies to all clients
|
||
|
|
served by the DHCP server)</caption><thead align="left"><tr><th colspan="2" valign="top" id="d0e61">Object</th>
|
||
|
|
<th valign="top" width="43.24324324324324%" id="d0e63">Value</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td rowspan="3" valign="top" width="13.513513513513514%" headers="d0e61 ">Configuration options</td>
|
||
|
|
<td valign="top" width="43.24324324324324%" headers="d0e61 ">option 1: Subnet mask</td>
|
||
|
|
<td valign="top" width="43.24324324324324%" headers="d0e63 ">255.255.255.0</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="43.24324324324324%" headers="d0e61 ">option 6: Domain name server</td>
|
||
|
|
<td valign="top" width="43.24324324324324%" headers="d0e63 ">10.1.1.10</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="43.24324324324324%" headers="d0e61 ">option 15: Domain name</td>
|
||
|
|
<td valign="top" width="43.24324324324324%" headers="d0e63 ">mycompany.com </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td colspan="2" valign="top" headers="d0e61 ">Is the server performing DNS updates?</td>
|
||
|
|
<td valign="top" width="43.24324324324324%" headers="d0e63 ">Yes -- Both A and PTR records</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td colspan="2" valign="top" headers="d0e61 ">Is the server supporting BOOTP clients?</td>
|
||
|
|
<td valign="top" width="43.24324324324324%" headers="d0e63 ">No</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="100%" frame="border" border="1" rules="all"><caption>Table 2. Subnet for Network Ring</caption><thead align="left"><tr><th colspan="2" valign="top" id="d0e102">Object</th>
|
||
|
|
<th valign="top" width="43.288590604026844%" id="d0e104">Value</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td colspan="2" valign="top" headers="d0e102 ">Subnet name</td>
|
||
|
|
<td valign="top" width="43.288590604026844%" headers="d0e104 ">NetworkSubnet</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td colspan="2" valign="top" headers="d0e102 ">Addresses to manage</td>
|
||
|
|
<td valign="top" width="43.288590604026844%" headers="d0e104 ">10.1.1.250 - 10.1.1.254</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td colspan="2" valign="top" headers="d0e102 ">Lease time</td>
|
||
|
|
<td valign="top" width="43.288590604026844%" headers="d0e104 ">24 hours (default)</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="13.422818791946309%" headers="d0e102 ">Configuration options</td>
|
||
|
|
<td valign="top" width="43.288590604026844%" headers="d0e102 ">Inherited options</td>
|
||
|
|
<td valign="top" width="43.288590604026844%" headers="d0e104 ">Options from Global configuration</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Other setup:</h4><p>Authorize
|
||
|
|
DHCP to send updates to DNS. Refer to Example: DNS and DHCP on the same iSeries server
|
||
|
|
in the DNS topic.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakgexampleparent.htm" title="By reviewing diagrams and examples of how different networks are set up, you can determine which is the best choice for your installation.">DHCP examples</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rzakgscenario7.htm" title="You can learn how to set up DHCP and DNS on two different iSeries servers to perform dynamic updates over a simple LAN.">Example: DNS and DHCP on different iSeries servers</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|