91 lines
6.4 KiB
HTML
91 lines
6.4 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="You can use your DHCP server in conjunction with your DNS server to dynamically update the client information in the DNS when DHCP assigns the client an IP address." />
|
||
|
|
<meta name="description" content="You can use your DHCP server in conjunction with your DNS server to dynamically update the client information in the DNS when DHCP assigns the client an IP address." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgconceptparent.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzakk/rzakkkickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzakk/rzakkconceptresourcerec.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgconfiguringdhcpdns.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzakk/rzakkplanningcoordinatingddns.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgplanningdemands.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgconfiguringdhcpdns.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgproblemddns.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="rzakgconceptddns" />
|
||
|
|
<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="rzakgconceptddns"><a name="rzakgconceptddns"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Dynamic updates</h1>
|
||
|
|
<div><p>You can use your DHCP server in conjunction with your DNS server
|
||
|
|
to dynamically update the client information in the DNS when DHCP assigns
|
||
|
|
the client an IP address.</p>
|
||
|
|
<p>Domain Name System (DNS) is a distributed database system
|
||
|
|
for managing host names and their associated IP addresses. DNS allows users
|
||
|
|
to locate hosts using simple names, such as www.example.com, rather than by
|
||
|
|
using the IP address (xxx.xxx.xxx.xxx).</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 the
|
||
|
|
client's DNS name to its IP address. The PTR record maps a host'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 will be 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 each client can update its A record.</div>
|
||
|
|
<p>Dynamic zones are secured by creating a list of authorized sources that
|
||
|
|
are allowed to send updates. 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,
|
||
|
|
different iSeries servers,
|
||
|
|
or to other servers that are capable of dynamic updates.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakgconceptparent.htm" title="DHCP interacts with clients and works in a network.">DHCP concepts</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakgplanningdemands.htm" title="You can plan for most of the DHCP setup by looking at your network topology, the devices on the network (for example, routers), and how you want to support your clients in DHCP.">Network topology considerations</a></div>
|
||
|
|
<div><a href="rzakgproblemddns.htm" title="The iSeries DHCP server is capable of dynamically updating DNS resource records. Dynamic update errors might be caused by the failure of DNS records update.">Problem: DNS records are not being updated by DHCP</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzakgconfiguringdhcpdns.htm" title="You can configure your DHCP and DNS servers to dynamically update DNS resource records when the DHCP server leases an IP address to a client.">Configure DHCP to send dynamic updates to DNS</a></div>
|
||
|
|
<div><a href="../rzakk/rzakkplanningcoordinatingddns.htm">Configure DNS to receive dynamic updates</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../rzakk/rzakkkickoff.htm">Domain Name System (DNS)</a></div>
|
||
|
|
<div><a href="../rzakk/rzakkconceptresourcerec.htm">Resource records</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|