66 lines
4.5 KiB
HTML
66 lines
4.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="concept" />
|
||
|
|
<meta name="DC.Title" content="Problem: DHCP job log has DNS030B messages with error code 3447" />
|
||
|
|
<meta name="abstract" content="Error code 3447 means that the DHCP server timed out waiting for a response from the DNS server. This might be due to network or connection problems between the iSeries DHCP server and DNS server." />
|
||
|
|
<meta name="description" content="Error code 3447 means that the DHCP server timed out waiting for a response from the DNS server. This might be due to network or connection problems between the iSeries DHCP server and DNS server." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgtroubleshooting.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="rzakgproblemjoblog" />
|
||
|
|
<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>Problem: DHCP job log has DNS030B messages with error code 3447</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakgproblemjoblog"><a name="rzakgproblemjoblog"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Problem: DHCP job log has DNS030B messages with error code 3447</h1>
|
||
|
|
<div><p>Error code 3447 means that the DHCP server timed out waiting for
|
||
|
|
a response from the DNS server. This might be due to network or connection
|
||
|
|
problems between the iSeries™ DHCP server and DNS server.</p>
|
||
|
|
<p>This message will be accompanied by a TCP5763 message which contains the
|
||
|
|
type of DNS resource record and detailed data for the resource record that
|
||
|
|
the DHCP server attempted to update.</p>
|
||
|
|
<p>Because the DHCP iSeries server attempts to update DNS resource records
|
||
|
|
each time a lease is renewed, the resource records might already be present
|
||
|
|
in the zone configuration file from the initial IP address lease or a prior
|
||
|
|
lease renewal. Check the DNS zone configuration data using a tool, such as
|
||
|
|
NSLOOKUP. You might find that the resource record is already present with
|
||
|
|
the correct data and that no action is necessary.</p>
|
||
|
|
<p>If the resource record is not present in DNS there are several ways to
|
||
|
|
update the resource record. The DHCP iSeries server will attempt to update
|
||
|
|
the resource record at the next lease renewal request. So, you can wait until
|
||
|
|
that occurs. Or, many clients attempt to renew or reacquire an IP address
|
||
|
|
when they are powered on. You might want to try to restart the
|
||
|
|
client, which can cause the DHCP server to attempt to update the DNS resource
|
||
|
|
records again.</p>
|
||
|
|
<p>If neither of these options work for you, you can update the DNS resource
|
||
|
|
records manually. This method is not recommended because the dynamic zone
|
||
|
|
must not be running when manual updates are made. So, other dynamic updates
|
||
|
|
from the DHCP server will be lost during this down-time. However, there are
|
||
|
|
dynamic update utilities provided by some client and BIND DNS server implementations.
|
||
|
|
You can use the dynamic update utility to update the resource record. While
|
||
|
|
similar in process to manually updating the zone (an administrator must enter
|
||
|
|
the resource record data to be updated), dynamic update utilities allow the
|
||
|
|
zone to be updated while the zone is active.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakgtroubleshooting.htm" title="You can view job log and trace data, as well as use troubleshooting lists for common problems.">Troubleshoot DHCP</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|