dhcpd 4.4 named ddns and additional event triggers
Hi folks, I'm using dhcp 4.4.1 with named ddns updating.
I'm researching performing additional triggers using event interface.
Older man pages state I cannot configure event statements if I'm using
internal ddns mechanism, however the man page for 4.4.1 just gives a terse description of events, and makes no mention whatsoever of whether event statements can be used in conjunction
with internal ddns mechanism:
REFERENCE: EVENTS There are three kinds of events that can happen regarding a lease, and it is possible to declare statements that occur when any of these events happen. These events are the commit event, when the server has made a commitment of a certain lease to a client, the release event, when the client has released the server from its commitment, and the expiry event, when the commitment expires.
To declare a set of statements to execute when an event happens, you must use the on state-ment, followed by the name of the event, followed by a series of statements to execute when the event happens, enclosed in braces.
Is it now possible to configure event declarations and still use internal ddns updating?
Thanks
_______________________________________________
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
Re: dhcpd 4.4 named ddns and additional event triggers
I've been using "on commit" along with DNS updating for years: on commit { log ( info, concat ( "Host:", pick-first-value(option
fqdn.hostname, option host-name, "(none)"), "=>",
pick-first-value(config-option server.ddns-hostname, "(none)") ," VendorId:", pick-first-value(option
vendor-class-identifier, "(none)") . . . )
); }
What is it that you want to do?
Bill
On 7/10/2020 3:15 PM, Rick Dicaire
wrote:
Hi folks, I'm using dhcp 4.4.1 with named ddns
updating.
I'm researching performing additional triggers using event
interface.
Older man pages state I cannot configure event statements
if I'm using
internal ddns mechanism, however the man page for 4.4.1
just gives a terse description of events, and makes no mention
whatsoever of whether event statements can be used in
conjunction
with internal ddns mechanism:
REFERENCE: EVENTS
There are three kinds of events that can happen
regarding a lease, and it is possible to declare
statements that occur when any of these events happen.
These events are the commit event, when the server has made
a commitment of a certain lease to a client, the
release event, when the client has released the server from
its commitment, and the expiry event, when the commitment
expires.
To declare a set of statements to execute when an
event happens, you must use the on state-ment, followed
by the name of the event, followed by a series of
statements to execute when the event happens, enclosed in
braces.
Is it now possible to
configure event declarations and still use internal ddns
updating?
_______________________________________________
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
Re: dhcpd 4.4 named ddns and additional event triggers
Bill, thanks for responding.
I'm looking to update netbox via REST api with dhcp client IPs/hostnames.
I expect to exec a script on each event type that will pass the IP and hostname data to netbox for updating.
My concern was configuring event actions would stop dhcpd from also updating named via dhcpd's internal
updating mechanism.
On Fri, Jul 10, 2020 at 11:53 PM Bill Shirley <[hidden email]> wrote:
I've been using "on commit" along with DNS updating for years: on commit { log ( info, concat ( "Host:", pick-first-value(option
fqdn.hostname, option host-name, "(none)"), "=>",
pick-first-value(config-option server.ddns-hostname, "(none)") ," VendorId:", pick-first-value(option
vendor-class-identifier, "(none)") . . . )
); }
What is it that you want to do?
Bill
On 7/10/2020 3:15 PM, Rick Dicaire
wrote:
Hi folks, I'm using dhcp 4.4.1 with named ddns
updating.
I'm researching performing additional triggers using event
interface.
Older man pages state I cannot configure event statements
if I'm using
internal ddns mechanism, however the man page for 4.4.1
just gives a terse description of events, and makes no mention
whatsoever of whether event statements can be used in
conjunction
with internal ddns mechanism:
REFERENCE: EVENTS
There are three kinds of events that can happen
regarding a lease, and it is possible to declare
statements that occur when any of these events happen.
These events are the commit event, when the server has made
a commitment of a certain lease to a client, the
release event, when the client has released the server from
its commitment, and the expiry event, when the commitment
expires.
To declare a set of statements to execute when an
event happens, you must use the on state-ment, followed
by the name of the event, followed by a series of
statements to execute when the event happens, enclosed in
braces.
Is it now possible to
configure event declarations and still use internal ddns
updating?
_______________________________________________
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
_______________________________________________
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.