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.
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.
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.
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.
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.