Fwd: Dynamic DNS/DHCP

[Glenn Satchell]

>X-YMail-OSG: 
Gbgrn5cVM1m0xxm3EJLlF22nmHn541meApaui6eGiabkMHyKkDIbSZJ_HSAxnYdnai19oB1NVBLkoCvD
A65zaTt8huauCQAoZA--
>Date: Fri, 18 Apr 2008 09:55:05 -0700 (PDT)
>From: frank miller <frankkmiller at yahoo.com>
>Subject: Re: Fwd: Dynamic DNS/DHCP
>To: dhcp-users at isc.org
>X-archive-position: 6105
>X-ecartis-version: Ecartis v1.0.0
>X-original-sender: frankkmiller at yahoo.com
>List-software: Ecartis version 1.0.0
>X-List-ID: <dhcp-users.isc.org>
>X-list: dhcp-users
>
>
>Thanks for help. Reverse updating fine, Forward giving
>error
>
>Forward map from HOST.DOMAIN to IP FAILED: Has an A
>record but no DHCID, not mine
>
>What I would like to have happen is that the update
>would occur based on the options in dhcpd.conf for
>that ethernet hardware address (ddns-hostname,
>ddns-domainname).
>
>I have 
>
>ddns-update-style interim;
>update-static-leases on;
>
>Thank you for help.

Probably the best way to get around this is to delete the existing A
record from DNS, then let dhcpd dynamically add it's own records.
Doing a release and renew on the client should be enough to force the
DNS update.

For forward records it adds the A record, plus a TXT record which
contains a hash of various identifiers (the DHCID) so that dhcpd can be
sure that next time it's updating a record that it put into the DNS
zone. The idea is to stop someone naming their PC with the same name as
an existing system, such as your Very Important Server, and modifying
the DNS entry.

regards,
-glenn