Provide a way to disable the creation of DHCID records by D2 (#455) · Issues · ISC Open Source Projects / Kea

Provide a way to disable the creation of DHCID records by D2

name: Feature request
about: Suggest an idea for this project

Some initial questions

Are you sure your feature is not already implemented in the latest Kea version? Nope
Are you sure what you would like to do is not possible using some other mechanisms? Yeah
Have you discussed your idea on kea-users or kea-dev mailing lists? Yep

Is your feature request related to a problem? Please describe. In an environment with multiple subnets, you may have static host reservations and the common dynamic 'user' reservations. For the static reservations, perhaps in a lab environment, the creation of the DHCID causes problems if something changes and the DNS record is not purged. For the dynamic 'user' reservation subnets, it is desired to keep the conflict resolution strategy prescribed by RFC 4703 enabled.

Describe the solution you'd like It would be helpful to disable the DHCP DDNS creation of DHCID records:

for reservations created from the static host table
for a specific subnet

Describe alternatives you've considered I suppose purging the DNS database of all DHCID records is the only easy workaround.

Additional context We use the static hosts for our lab equipment. In some cases, like where we make a change to the host database entry, moving the address to a different host, the new host cannot update the DNS record with new information, because the old DHCID locks the A and PTR records from being updated.

Funding its development Kea is run by ISC, which is a small non-profit organization without any government funding or any permanent sponsorship organizations. Are you able and willing to participate financially in the development costs? Not at this time

Participating in development Are you willing to participate in the feature development? ISC team always tries to make a feature as generic as possible, so it can be used in wide variety of situations. That means the proposed solution may be a bit different that you initially thought. Are you willing to take part in the design discussions? Are you willing to test an unreleased engineering code? Yes

Contacting you How can ISC reach you to discuss this matter further? If you do not specify any means such as e-mail, jabber id or a telephone, we may send you a message on github with questions when we have them. My email is in the kea-users list.

---
name: Feature request
about: Suggest an idea for this project

---

**Some initial questions**
- Are you sure your feature is not already implemented in the latest Kea version? Nope
- Are you sure what you would like to do is not possible using some other mechanisms? Yeah
- Have you discussed your idea on kea-users or kea-dev mailing lists? Yep

**Is your feature request related to a problem? Please describe.**
In an environment with multiple subnets, you may have static host reservations and the common dynamic 'user' reservations. For the static reservations, perhaps in a lab environment, the creation of the DHCID causes problems if something changes and the DNS record is not purged. 
For the dynamic 'user' reservation subnets, it is desired to keep the conflict resolution strategy prescribed by RFC 4703 enabled.

**Describe the solution you'd like**
It would be helpful to **disable** the DHCP DDNS creation of DHCID records:
1) for reservations created from the static host table
2) for a specific subnet

**Describe alternatives you've considered**
I suppose purging the DNS database of all DHCID records is the only easy workaround.

**Additional context**
We use the static hosts for our lab equipment. In some cases, like where we make a change to the host database entry, moving the address to a different host, the new host cannot update the DNS record with new information, because the old DHCID locks the A and PTR records from being updated.

**Funding its development**
Kea is run by ISC, which is a small non-profit organization without any government funding or any permanent sponsorship organizations. Are you able and willing to participate financially in the development costs? Not at this time

**Participating in development**
Are you willing to participate in the feature development? ISC team always tries to make a feature as generic as possible, so it can be used in wide variety of situations. That means the proposed solution may be a bit different that you initially thought. Are you willing to take part in the design discussions? Are you willing to test an unreleased engineering code? Yes

**Contacting you**
How can ISC reach you to discuss this matter further? If you do not specify any means such as e-mail, jabber id or a telephone, we may send you a message on github with questions when we have them. My email is in the kea-users list.

Discussion
Designs

The one place for your designs

To upload designs, you'll need to enable LFS. More information