104 lines
7.8 KiB
HTML
104 lines
7.8 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="concept" />
|
||
|
|
<meta name="DC.Title" content="Dynamic updates" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakkconceptparent.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakkscenario3.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzakg/rzakgkickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakkconceptresourcerec.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakkplanningcoordinatingddns.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzakg/rzakgconfiguringdhcpdns.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/qtobupdt.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakkconceptbind.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="rzakkconceptdynamic" />
|
||
|
|
<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>Dynamic updates</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakkconceptdynamic"><a name="rzakkconceptdynamic"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Dynamic updates</h1>
|
||
|
|
<div><p>OS/400<sup>®</sup> 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.</p>
|
||
|
|
<p>DHCP is a TCP/IP standard that uses a central server to manage IP addresses
|
||
|
|
and other configuration details for an entire network. A DHCP server responds
|
||
|
|
to requests from clients, dynamically assigning properties to them. DHCP allows
|
||
|
|
you to define network host configuration parameters at a central location
|
||
|
|
and automate the configuration of hosts. It is often used to assign temporary
|
||
|
|
IP addresses to clients for networks that contain more clients than the number
|
||
|
|
of IP addresses available.</p>
|
||
|
|
<p>In the past, all DNS data was stored in static databases. All DNS resource
|
||
|
|
records had to be created and maintained by the administrator. Now, DNS servers
|
||
|
|
running BIND 8 can be configured to accept requests from other sources to
|
||
|
|
update zone data dynamically.</p>
|
||
|
|
<p>You can configure your DHCP server to send update requests to the DNS server
|
||
|
|
each time it assigns a new address to a host. This automated process reduces
|
||
|
|
DNS server administration in rapidly growing or changing TCP/IP networks,
|
||
|
|
and in networks where hosts change locations frequently. When a client using
|
||
|
|
DHCP receives an IP address, that data is immediately sent to the DNS server.
|
||
|
|
Using this method, DNS can continue to successfully resolve queries for hosts,
|
||
|
|
even when their IP addresses change.</p>
|
||
|
|
<p>You can configure DHCP to update address mapping (A) records, reverse-lookup
|
||
|
|
pointer (PTR) records, or both on behalf of a client. The A record maps a
|
||
|
|
machine's host name to its IP address. The PTR record maps a machine's IP
|
||
|
|
address to its host name. When a client's address changes, DHCP can automatically
|
||
|
|
send an update to the DNS server so other hosts in the network can locate
|
||
|
|
the client through DNS queries at its new IP address. For each record that
|
||
|
|
is updated dynamically, an associated Text (TXT) record is written to identify
|
||
|
|
that the record was written by DHCP.</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 every 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>Dynamic zones are secured by creating a list of authorized sources that
|
||
|
|
are allowed to send updates. You can define authorized sources using individual
|
||
|
|
IP addresses, whole subnets, packets that have been signed using a shared
|
||
|
|
secret key (called a <em>Transaction Signature</em>, or TSIG), or any combination
|
||
|
|
of those methods. DNS verifies that incoming request packets are coming from
|
||
|
|
an authorized source before updating the resource records.</p>
|
||
|
|
<p>Dynamic updates can be performed between DNS and DHCP on a single iSeries™ server,
|
||
|
|
between different iSeries servers, or between an iSeries and
|
||
|
|
other servers that are capable of dynamic updates.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> The dynamic update application programming interface (API) QTOBUPT is
|
||
|
|
required on servers that are sending dynamic updates to DNS. It is installed
|
||
|
|
automatically with i5/OS™ Option 31, DNS.</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakkconceptparent.htm" title="This topic explains what Domain Name System (DNS) is and how it works. It also shows the different types of zones that can be defined on a DNS server.">Domain Name System concepts</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="../rzakg/rzakgkickoff.htm">Dynamic Host Configuration Protocol (DHCP)</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzakkplanningcoordinatingddns.htm" title="Domain Name System (DNS) servers running BIND 8 can be configured to accept requests from other sources to update zone data dynamically. This topic provides instructions for configuring the allow-update option so DNS can receive dynamic updates.">Configure Domain Name System to receive dynamic updates</a></div>
|
||
|
|
<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="rzakkscenario3.htm" title="This example depicts Domain Name System (DNS) and Dynamic Host Configuration Protocol (DHCP) on the same server.">Example: Domain Name System and Dynamic Host Configuration Protocol on the same iSeries server</a></div>
|
||
|
|
<div><a href="rzakkconceptresourcerec.htm" title="This topic explains how resource records are used by Domain Name System (DNS). Resource records are used to store data about domain names and IP addresses. This topic contains a searchable list of resource records supported for OS/400 V5R1.">Domain Name System resource records</a></div>
|
||
|
|
<div><a href="../apis/qtobupdt.htm">QTOBUPT</a></div>
|
||
|
|
<div><a href="rzakkconceptbind.htm" title="Besides dynamic updates, BIND 8 offers several features to enhance performance of your Domain Name System (DNS) server.">BIND 8 features</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|