IPv6 DDNS using dhcp-4.1.0p1

[brett lee]

Hello - Have a couple questions on DHCPD / DDNS.  

1.  Cannot seem to get DDNS working for some v6 pools.  Per the logs, updates are not being sent from DHCPD and are not arriving at NAMED.  Both are on the same host and the config files dhcpd.conf and named.conf are below.  Hoping someone can point out what is misconfigured.

2.  Cannot seem to assign a fixed address.  All hosts (Solaris, FreeBSD, Win2K8) only get addresses from the dynamic range.  The config below attempts to define an address for the host freebsd8vm.  Have pulled what I believe to be the dhcp6.client-id from the DHCPD logging seen here:

Release message from fe80::20c:29ff:fef4:8684 port 546, transaction ID 0x7DDE96
Client 00:01:00:01:12:e6:2d:3c:00:0c:29:f4:86:84 releases address 2bad:0:564:1::16

3.  On a DHCPDv4 server with DDNS working, the master file for each zone is reformatted/rewritten.  Is there an option to stop this, or is it an artifact of the DDNS implementation?

Thanks!  -Brett

== /dhcp-4.1.0p1 dhcpd.conf ==
authoritative;

include "/etc/rndc.key";
ddns-updates            on;
ddns-update-style       interim;
ddns-domainname         "ipv6.apevt.local";
ddns-rev-domainname     "in-addr.arpa";
ignore                  client-updates;

zone ipv6.apevt.local. {
        primary 192.168.1.23;
        key "rndc-key";
}
log-facility local6;
min-lease-time 60;
default-lease-time 3600;
max-lease-time 43200;

option domain-name "ipv6.apevt.local";
option domain-name-servers 192.168.1.254, 192.168.1.23;
option dhcp.domain-search "ipv6.apevt.local, apevt.local";
option dhcp6.domain-search "ipv6.apevt.local, apevt.local";
option dhcp6.name-servers 2bad:0:564:1:203:baff:fee8:36f2, 2bad:0:564:2:203:baff:fee8:36f3, 2bad:0:564:3:203:baff:fee8:36f4;

subnet6 2bad:0000:0564:0001::/64 {
   allow unknown-clients;
   min-lease-time 60;
   default-lease-time 600;
   max-lease-time 600;
   range6 2bad:0000:0564:0001::10 2bad:0000:0564:0001::19;
   host freebsd8vm {
     host-identifier option dhcp6.client-id "05:00:00:00:31:00:00:00:03:00:00:00:00:00:00:00";
     fixed-address6  2bad:0000:0564:0001::21;
   }
}


=== BIND 9.3.4 /etc/named.conf ===
options {
        directory "/var/named";
        forwarders {
                    192.168.1.254;
        };
};
logging {
        channel default {
                file "/var/named/log.default" versions 2 size 5m;
                severity info;
                print-severity yes;
                print-time yes;
                print-category yes;
        };
        category default {
                default_syslog;
                default;
        };
        channel queries {
                file "/var/named/log.queries" versions 3 size 2m;
                severity info;
        };
        category queries {
                queries;
        };
};
controls {
        inet 127.0.0.1 allow { localhost; } keys { rndc-key; };
};
zone "." IN {
        type hint;
        file "named.ca";
};
zone "localhost" IN {
        type master;
        file "localhost.zone";
        allow-update { none; };
};
zone "0.0.127.in-addr.arpa" IN {
        type master;
        file "db.127.0.0";
        allow-update { none; };
};
zone "apevt.local" IN {
        type slave;
        file "apevt.local";
        masters {192.168.1.254; };
};
zone "ipv6.apevt.local" IN {
        type master;
        file "ipv6.apevt.local";
        allow-update { key "rndc-key"; };
        allow-transfer { 192.168.1.254; };
        also-notify { 192.168.1.254; };
};
zone "1.168.192.in-addr.arpa" IN {
        type slave;
        file "db.192.168.1";
        masters {192.168.1.254; };
};
zone "2.168.192.in-addr.arpa" IN {
        type slave;
        file "db.192.168.2";
        masters {192.168.1.254; };
};
zone "3.168.192.in-addr.arpa" IN {
        type slave;
        file "db.192.168.3";
        masters {192.168.1.254; };
};
include "/etc/rndc.key";