force DDNS update

[Jason Gerdes]

Hello,

I have been lurking here for a while with a similar issue.  I have some 'stale' or nonexistent ddns records with the same setup.  Is there a way to clear out all of the old mappings and just start fresh, so to speak.  I have some network scripts that rely on the hostname to be correct and this problem is wreaking havok on those processes.  I have been receiving this error message in my logs that I think might possibly help with the diagnosis:

update failed: 'name not in use' prerequisite not satisfied (YXDOMAIN)

I have googled this message in every way that I know how without finding any useful information.  Please help if you can.


--Jason

>>> Carl Karsten <carl at personnelware.com> 4/22/2007 6:10 PM >>>
My dhcp/ddns setup does almost exactly what I want it to.  I think I have one 
little kink to work out:  when the IP of a box changes, bind doesn't pickup the 
change.

If you are wondering: why does the IP change?  good Q.  I have a few A's:

1. duel boot box, both boots have the same hosthame (perhaps I should change 
this)  I boot into Win, it sends hostname=foo and gets IP 1.1.1.1.  I shut that 
down (it does not release the lease on .1) and boot into linux, it sends 
hostname=foo and gets IP 1.1.1.2.

2. I move a box from the IP pool to a fixed IP using dhcp.conf
fixed-address 192.168.1.6 ;

3. swap nic, so new mac.

4. magic?

In any event, anytime dhcpd tells bind foo=X, I don't want bind to argue.  I 
want it to take the new IP and make it so.

the ddns part of /etc/dhcp3/dhcpd.conf:

ddns-updates on;
ddns-update-style interim;
do-forward-updates on;
ddns-domainname "personnelware.com";
ddns-rev-domainname "in-addr.arpa.";
update-static-leases on;
# ddns-ttl 7200;

key DHCP_UPDATER {
         algorithm HMAC-MD5.SIG-ALG.REG.INT;
         secret ZiO1XpvhIDVLRsvnBk9+Qw==;
        };

zone personnelware.com. {
         primary localhost;
         key DHCP_UPDATER;
        }

zone 1.168.192.in-addr.arpa. {
         primary localhost;
          key DHCP_UPDATER;
        }


guessing the only important part of bind.conf:

zone "personnelware.com" {
         type master;
         file "/etc/bind/personnelware.com.db";
         allow-update { key DHCP_UPDATER; };
        };