DDNS with v6 & v4

Tim Dean Tim.Dean at wal-mart.com
Thu Jan 27 18:57:24 UTC 2011


I've found that, at the moment, a workaround method to handle this DDNS update issue between v4 and v6 clients is to segregate the zones.  (Example:  Insert v4 clients into "vulture.test" and v6 clients into a new zone called "ipv6.vulture.test".)

AFAIK this is a known issue with the current DDNS implementation in ISC DHCP 4.2.0-P2.  (Not sure which version is built into RHEL6.)



From: Jarrod Johnson
Sent: Thursday, January 27, 2011 12:22 PM
To: Users of ISC DHCP
Subject: DDNS with v6 & v4

So I have dhcpd running for IPv4 and another for IPv6.  When a client performs the first DHCP (in this example, IPv6) and triggers the dhcp server to do the ddns up, all is well:
Jan 27 10:48:54 cirrus named[5315]: client 192.168.127.253#54564: signer "xcat_key" approved
Jan 27 10:48:54 cirrus named[5315]: client 192.168.127.253#54564: updating zone 'vulture.test/IN': adding an RR at 'h04.vulture.test' AAAA
Jan 27 10:48:54 cirrus named[5315]: client 192.168.127.253#54564: updating zone 'vulture.test/IN': adding an RR at 'h04.vulture.test' TXT
Jan 27 10:48:54 cirrus dhcpd: Added new forward map from h04.vulture.test to fd2d:c747:f314:d001:7843:4154:ef39:de38


However when the client subsequently does the IPv4 address, it refuses to do the A record:

Jan 27 10:49:45 cirrus named[5315]: client 192.168.127.253#43968: updating zone 'vulture.test/IN': update unsuccessful: h04.vulture.test: 'name not in use' prerequisite not satisfied (YXDOMAIN)
Jan 27 10:49:45 cirrus named[5315]: client 192.168.127.253#47226: updating zone 'vulture.test/IN': update unsuccessful: h04.vulture.test/TXT: 'RRset exists (value dependent)' prerequisite not satisfied (NXRRSET)
Jan 27 10:49:45 cirrus dhcpd: Forward map from h04.vulture.test to 192.168.72.4 FAILED: Has an address record but no DHCID, not mine.


If I scrub everything clean, everything will be fine for the A record, but I cannot seem to make the DHCP servers handle both the A and the AAAA record at the same time.  Is there a way to take care of this?  This is the dhcpd variant as shipped by Red Hat in RHEL6.
This email and any files transmitted with it are confidential and
intended solely for the individual or entity to whom they are
addressed. If you have received this email in error destroy it
immediately.

                                               *** Walmart
Confidential ***





More information about the dhcp-users mailing list