[No need to cc me in replies. I'll read replies on the list.]
--On Wednesday, March 09, 2022 2:50 PM + "Frey, Rick E"
wrote:
Prevent DDNS updates on DNS server for specified zones/names. Not sure
what nameserver you're using but BIND can be configured to prevent DDNS
updates at individ
While perhaps not ideal, if you have control over what the static
clients send in their DHCP requests, having them send an FQDN option
with the N-S flags to N=1, S=0 would tell the server to not do any
updates. See this section:
https://kea.readthedocs.io/en/latest/arm/dhcp4-srv.html#when-doe
I first wondered if something could be done in a class but as you mention, docs
indicate that ddns-send-updates directive is limited to subnet as lowest level
so doesn’t look there is much options in current Kea config.
Other options:
* Have clients with host reservation set option 81 bits
Kenneth Porter writes:
> I've enabled DDNS for my subnet but I don't want it used for reservations,
> only for the pool. The DNS entries for reservations are manually entered in
> my DNS in a higher-level domain. (The pool is entered in the "dhcp"
> subdomain which allows updates.)
>
> My subnet
I've enabled DDNS for my subnet but I don't want it used for reservations,
only for the pool. The DNS entries for reservations are manually entered in
my DNS in a higher-level domain. (The pool is entered in the "dhcp"
subdomain which allows updates.)
My subnet is a /16 and the pool is a speci