From 7fffbde16ad1a8d587a1af2f8ac16bf6517667f3 Mon Sep 17 00:00:00 2001 From: Shawn Routhier Date: Fri, 13 Jun 2014 09:16:00 -0700 Subject: [master] Clean up DDNS description Remove the text about use-host-decl-names within DDNS. This appears to have been correct when describing the ad-hoc DDNS option but not the interim or standard options. In the future we may choose to enhance the latter two but for now we shouldn't claim we do things we don't. --- server/dhcpd.conf.5 | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) (limited to 'server') diff --git a/server/dhcpd.conf.5 b/server/dhcpd.conf.5 index be624792..2c63f9c7 100644 --- a/server/dhcpd.conf.5 +++ b/server/dhcpd.conf.5 @@ -1159,20 +1159,16 @@ sends a fully-qualified domain name in the \fBfqdn\fR option, the server uses only the leftmost part of the domain name - in the example above, "jschmoe" instead of "jschmoe.radish.org". .PP +If the defaults for choosing the host name are not appropriate +you can write your own statement to set the ddns-hostname variable +as you wish. +.PP Further, if the \fIignore client-updates;\fR directive is used, then the server will in addition send a response in the DHCP packet, using the FQDN Option, that implies to the client that it should perform its own updates if it chooses to do so. With \fIdeny client-updates;\fR, a response is sent which indicates the client may not perform updates. .PP -Also, if the -.I use-host-decl-names -configuration option is enabled, then the host declaration\'s -.I hostname -will be used in place of the -.I hostname -option, and the same rules will apply as described above. -.PP Both the standard and interim options also include a method to allow more than one DHCP server to update the DNS database without accidentally deleting A records that shouldn\'t be deleted nor failing -- cgit v1.2.1