From 2a8eb95d8bf43cf8b12ee064c7bc1d483b4cd34b Mon Sep 17 00:00:00 2001 From: Johannes Date: Tue, 17 Nov 2020 09:13:41 +0100 Subject: [PATCH] Fixed typo --- docs/design_pages/active_directory_dns_updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/design_pages/active_directory_dns_updates.md b/docs/design_pages/active_directory_dns_updates.md index f5027ea..6b242ef 100644 --- a/docs/design_pages/active_directory_dns_updates.md +++ b/docs/design_pages/active_directory_dns_updates.md @@ -107,7 +107,7 @@ One change compared to the IPA code would be that IPA only sends the refresh whe During design discussion, it was decided that the new options should be not include the provider-specific prefix but rather be provider agnostic to ease sharing the code and possibly allow other providers to use dynamic DNS updates as well. The new options are: -1. `dynds_update` `(bool)` - whether to perform the dynamic DNS update. Defaults to false. +1. `dyndns_update` `(bool)` - whether to perform the dynamic DNS update. Defaults to false. 2. `dyndns_refresh_interval` `(integer)` - how often to run the periodic task to refresh the resource record 3. `dyndns_iface` `(string)` - instead of updating the DNS with the address used to connect to LDAP, which is the default, use all addresses configured on a particular interface 4. `dyndns_update_ptr` `(bool)` - whether to also update the reverse zone when updating the forward zone