DHCP 4.2 DDNS - zone statements

Shawn Routhier sar at isc.org
Tue Feb 12 17:59:38 UTC 2013

On Feb 12, 2013, at 9:33 AM, <greg.rabil at bt.com> <greg.rabil at bt.com> wrote:

> Hello ISC DHCP Users,
> With the DHCP 4.1 server, we have been able to have DDNS updates occur for the leases *without* having zone { } statements for each forward and reverse zone to be updated.  This works because the resolver on the host (i.e. resolv.conf) points to the nameserver that is authoritative for the dynamic zones to be updated.
> However, with the exact same configuration, the DHCP 4.2 server fails to perform the updates.  It reports the following error:
> dhcpd: Unable to add forward map from test1.example.com to not found
> If the zone { } statements listing the primary DNS server’s IP are explicitly added for the dynamic zones, then the updates succeed.
> I have found a similar problem reported here: https://lists.isc.org/pipermail/dhcp-users/2012-April/015405.html
> My question is if this is a known issue/bug with 4.2?  I did not find any release notes that indicate that the zone {} statements are now required.  Can anyone confirm if this behavior was changed on purpose?
> Thanks,
> Greg
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users

It is a known issue.  It was not intentional.  

I believe most people include zone statements so 
I'm not sure how many people are affected by this change
so I'm not sure if and when we shall work on it.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20130212/74b4c555/attachment.html>

More information about the dhcp-users mailing list