From 6772e5f8e3172e5fa962c036c4d7089989b9a737 Mon Sep 17 00:00:00 2001
From: rebortg <github@ghlr.de>
Date: Mon, 27 Jun 2022 21:23:34 +0200
Subject: dns: add missing commands

---
 docs/configuration/service/dns.rst | 36 ++++++++++++++++++++++++++----------
 1 file changed, 26 insertions(+), 10 deletions(-)

(limited to 'docs/configuration/service/dns.rst')

diff --git a/docs/configuration/service/dns.rst b/docs/configuration/service/dns.rst
index c012435b..23634824 100644
--- a/docs/configuration/service/dns.rst
+++ b/docs/configuration/service/dns.rst
@@ -21,6 +21,10 @@ avoid being tracked by the provider of your upstream DNS server.
    Forward incoming DNS queries to the DNS servers configured under the ``system
    name-server`` nodes.
 
+.. cfgcmd:: set service dns forwarding dhcp <interface>
+
+   Interfaces whose DHCP client nameservers to forward requests to.
+
 .. cfgcmd:: set service dns forwarding name-server <address>
 
    Send all DNS queries to the IPv4/IPv6 DNS server specified under `<address>`.
@@ -35,6 +39,15 @@ avoid being tracked by the provider of your upstream DNS server.
 
    .. note:: This also works for reverse-lookup zones (``18.172.in-addr.arpa``).
 
+.. cfgcmd:: set service dns forwarding domain <domain-name> addnta
+
+   Add NTA (negative trust anchor) for this domain. This must be set if the
+   domain does not support DNSSEC.
+
+.. cfgcmd:: set service dns forwarding domain <domain-name> recursion-desired
+
+   Set the "recursion desired" bit in requests to the upstream nameserver.
+
 .. cfgcmd:: set service dns forwarding allow-from <network>
 
    Given the fact that open DNS recursors could be used on DDoS amplification
@@ -191,34 +204,32 @@ Configuration
 :rfc:`2136` Based
 -----------------
 
-.. cfgcmd:: set service dns dynamic interface <interface> rfc2136 <service-name>
-
-   Create new :rfc:`2136` DNS update configuration which will update the IP
-   address assigned to `<interface>` on the service you configured under
-   `<service-name>`.
+Create new :rfc:`2136` DNS update configuration which will update the IP
+address assigned to `<interface>` on the service you configured under
+`<service-name>`.
 
 .. cfgcmd:: set service dns dynamic interface <interface> rfc2136 <service-name>
    key <keyfile>
 
    File identified by `<keyfile>` containing the secret RNDC key shared with
-   remote DNS server.
+   remote DNS server. This is a required option.
 
 .. cfgcmd:: set service dns dynamic interface <interface> rfc2136 <service-name>
    server <server>
 
    Configure the DNS `<server>` IP/FQDN used when updating this dynamic
-   assignment.
+   assignment.  This is a required option.
 
 .. cfgcmd:: set service dns dynamic interface <interface> rfc2136 <service-name>
-   zone <zone>
+   zone <zone> 
 
-   Configure DNS `<zone>` to be updated.
+   Configure DNS `<zone>` to be updated.  This is a required option.
 
 .. cfgcmd:: set service dns dynamic interface <interface> rfc2136 <service-name>
    record <record>
 
    Configure DNS `<record>` which should be updated. This can be set multiple
-   times.
+   times. This is a required option.
 
 .. cfgcmd:: set service dns dynamic interface <interface> rfc2136 <service-name>
    ttl <ttl>
@@ -308,6 +319,11 @@ hostnames, protocol and server.
    When a ``custom`` DynDNS provider is used the `<server>` where update
    requests are being sent to must be specified.
 
+.. cfgcmd:: set service dns dynamic interface <interface> service <service>
+   zone <zone>
+
+   Set the DNS zone to update. This is only available with CloudFlare.
+
 Example:
 ^^^^^^^^
 
-- 
cgit v1.2.3