See RT ticket #17103 for more.
Changes since 4.0.0a2
+- The DHCP server no longer requires a "ddns-update-style" statement,
+ and now defaults to "none", which means DNS updates are disabled.
+
- Fix for startup where there are no IPv4 addresses on an interface.
Thanks to Marcus Goller for reporting the bug.
data_string_forget (&db, MDL);
}
} else {
- log_info ("%s", "");
- log_error ("** You must add a global ddns-update-style %s%s.",
- "statement to ", path_dhcpd_conf);
- log_error (" To get the same behaviour as in 3.0b2pl11 %s",
- "and previous");
- log_error (" versions, add a line that says \"%s\"",
- "ddns-update-style ad-hoc;");
- log_fatal (" Please read the dhcpd.conf manual page %s",
- "for more information. **");
+ ddns_update_style = DDNS_UPDATE_STYLE_NONE;
}
oc = lookup_option (&server_universe, options, SV_LOG_FACILITY);
.\" see ``http://www.vix.com''. To learn more about Nominum, Inc., see
.\" ``http://www.nominum.com''.
.\"
-.\" $Id: dhcpd.conf.5,v 1.87 2007/07/20 19:18:24 dhankins Exp $
+.\" $Id: dhcpd.conf.5,v 1.88 2007/09/17 10:13:07 shane Exp $
.\"
.TH dhcpd.conf 5
.SH NAME
The \fIddns-update-style\fR statement is only meaningful in the outer
scope - it is evaluated once after reading the dhcpd.conf file, rather
than each time a client is assigned an IP address, so there is no way
-to use different DNS update styles for different clients.
+to use different DNS update styles for different clients. The default
+is \fBnone\fR.
.RE
.PP
.B The