109 lines
7.1 KiB
HTML
109 lines
7.1 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: Domain Name System and Dynamic Host Configuration Protocol on the same iSeries server" />
|
||
|
|
<meta name="abstract" content="This example depicts Domain Name System (DNS) and Dynamic Host Configuration Protocol (DHCP) on the same server." />
|
||
|
|
<meta name="description" content="This example depicts Domain Name System (DNS) and Dynamic Host Configuration Protocol (DHCP) on the same server." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakkexampleparent.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzakg/rzakgscenario7.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakkconceptdynamic.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakkplanningdomainstructure.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzakg/rzakgconfiguringdhcpdns.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="rzakkscenario3" />
|
||
|
|
<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: Domain Name System and Dynamic Host Configuration Protocol
|
||
|
|
on the same iSeries server</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakkscenario3"><a name="rzakkscenario3"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Example: Domain Name System and Dynamic Host Configuration Protocol
|
||
|
|
on the same iSeries server</h1>
|
||
|
|
<div><p>This example depicts Domain Name System (DNS) and Dynamic Host
|
||
|
|
Configuration Protocol (DHCP) on the same server.</p>
|
||
|
|
<div class="section"><p>The configuration can be used to update DNS zone data dynamically
|
||
|
|
when DHCP assigns IP addresses to hosts.</p>
|
||
|
|
<p>The following figure depicts
|
||
|
|
a small subnet network with one iSeries™ server acting as a DHCP and DNS
|
||
|
|
server to four clients. 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"><span class="figcap">Figure 1. DNS and DHCP on the same iSeries server</span><br /><img src="rzakk502.gif" alt="DNS and DHCP on the same iSeries server." /><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
|
||
|
|
will be unable to map a network drive to its host name because the DNS records
|
||
|
|
will contain the file server's previous IP address.</p>
|
||
|
|
<p>With the OS/400<sup>®</sup> V5R1
|
||
|
|
DNS server based on BIND 8, you can configure your DNS zone to accept dynamic
|
||
|
|
updates to 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
|
||
|
|
will be 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>To
|
||
|
|
configure a DNS zone to accept dynamic updates, complete the following tasks:</p>
|
||
|
|
<ul><li>Identify the dynamic zone<p>You cannot manually update a dynamic zone
|
||
|
|
while the server is running. Doing so might cause interference with incoming
|
||
|
|
dynamic updates. Manual updates can be made when the server is stopped, but
|
||
|
|
you will lose any dynamic updates sent while the server is down. For this
|
||
|
|
reason, you might want to configure a separate dynamic zone to minimize the
|
||
|
|
need for manual updates. See<a href="rzakkplanningdomainstructure.htm#rzakkplanningdomainstructure">Determine domain structure</a> for
|
||
|
|
more information about configuring your zones to use the dynamic update function.</p>
|
||
|
|
</li>
|
||
|
|
<li>Configure the allow-update option<p>Any zone with the allow-update option
|
||
|
|
configured is considered a dynamic zone. The allow-update option is set on
|
||
|
|
a per-zone basis. To accept dynamic updates, the allow-update option must
|
||
|
|
be enabled for this zone. For this example, the mycompany.com zone has allow-update
|
||
|
|
data, but other zones defined on the server can be configured to be static
|
||
|
|
or dynamic.</p>
|
||
|
|
</li>
|
||
|
|
<li>Configure DHCP to send dynamic updates<p>You must authorize your DHCP
|
||
|
|
server to update the DNS records for the IP addresses it has distributed.</p>
|
||
|
|
</li>
|
||
|
|
<li>Configure secondary server update preferences<p>To keep secondary servers
|
||
|
|
current, you can configure DNS to use the NOTIFY function to send a message
|
||
|
|
to secondary servers for the mycompany.com zone when zone data changes. You
|
||
|
|
should also configure incremental zone transfers (IXFR), which enables IXFR-enabled
|
||
|
|
secondary servers to track and load only the updated zone data, instead of
|
||
|
|
the entire zone.</p>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
<p>If you run DNS and DHCP on different servers, there are some additional
|
||
|
|
configuration requirements for the DHCP server.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakkexampleparent.htm" title="You can use these examples to understand how to use Domain Name System (DNS) in your network.">Domain Name System examples</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakkconceptdynamic.htm" title="OS/400 V5R1 DNS based on BIND 8 supports dynamic updates. These allow outside sources, such as Dynamic Host Configuration Protocol (DHCP), to send updates to the Domain Name System (DNS) server.">Dynamic updates</a></div>
|
||
|
|
<div><a href="rzakkplanningdomainstructure.htm" title="If you are setting up a domain for the first time, you should plan for demand and maintenance before creating zones.">Determine domain structure</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="../rzakg/rzakgconfiguringdhcpdns.htm">Configuring DHCP to send dynamic updates</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../rzakg/rzakgscenario7.htm">Example: DNS and DHCP on different iSeries servers</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|