By default, computers that are statically configured for TCP/IP attempt to dynamically register host (A) resource records and pointer (PTR) resource records for IP addresses that are configured and used by their installed network connections.
By default, all computers register records based on their fully qualified domain name (FQDN).
It’s also quite reasonable to setup your main domain as a regular domain, and use two subdomains, one for IPv4 and one for IPv6. On Free BSD edit /etc/namedb/named.conf: [cc] $ cat /etc/namedb/options ; include “/etc/namedb/rndc.key”; controls ; zone “.” ; zone “example.com” ; zone “1.168.192.in-addr.arpa” ; zone “0.0.b.e.e.0.0.f.8. D.0.1.0.0.2.ip6.arpa” ; [/cc] The above is an edited example.
Also, don't reload named, restart named when debugging. A few minor changes are necesary to your (isc dhcp3 server).
First, in the global portion: requests an address via dhcp, the dhcp server will tell the dns server.
This article will cover how to setup dns with dynamic updates aswell as configuring your dhcp server to push updates to it aswell. If there's anything this article doesn't cover with respect to what you are looking for, leave a comment and I'll do what I can.
I assume you already know how to setup plain old dns aswell as plain old dhcp. Dynamic DNS is the means by which to push new records into your dns server while it is running, without having to edit any zone files.
So I've given up trying to resolve that issue with the tool a pain, anyway; it was too inflexible with how you entered data, and quite confusing as to how you were supposed to use it (poor documentation, as usual, didn't help). This time I tried to do something else, something that did work on Red Hat 9.0: Setting up a slave zone, and getting it to populate its records from some other master server (this was just an experiment just to see how it worked, for curiosity's sake).
I kept getting very badly worded error messages about it failing while receiving data (see below), which seemed to indicate that it wasn't receiving the data, but the real problem was that it couldn't write the data to a file on the local disk, despite me playing fast and loose with ownership and permissions for the directories it was working in (trying to resolve that error message).
Domain Name System (DNS) client computers can use dynamic update to register and dynamically update their resource records with a DNS server whenever changes occur.
This reduces the need for manual administration of zone records, especially for clients that frequently move or change locations and use Dynamic Host Configuration Protocol (DHCP) to obtain an IP address.
I installed Fedora Core 2 Linux on another that's totally under my control.
Fedora Core 2 Linux has now been superceded by Fedora Core 3, and I've wiped off my Fedora Core 2 installation, updating to Fedora Core 3.
The primary full computer name, an FQDN, is based on the primary DNS suffix of a computer,appended to its computer name.