diff --git a/DnsServerCore/www/index.html b/DnsServerCore/www/index.html index ea2ab260..5711040d 100644 --- a/DnsServerCore/www/index.html +++ b/DnsServerCore/www/index.html @@ -834,6 +834,7 @@ + @@ -987,6 +988,14 @@
The default TTL value to use if not specified when adding or updating records in a Zone.
+
+ +
+ +
+
The default SOA Responsible Person email address to use when adding a Primary Zone.
+
+
@@ -1011,7 +1020,7 @@
-
Enter IP addresses or network addresses one below another that are allowed to Notify all secondary zones.
+
Enter IP addresses or network addresses one below another that are allowed to Notify all Secondary Zones.
@@ -1307,7 +1316,7 @@
-
Specify a PKCS #12 certificate (.pfx) file path on the server. The path can be relative to the DNS server's config folder. The certificate must contain private key.
+
Specify a PKCS #12 certificate (.pfx or .p12) file path on the server. The path can be relative to the DNS server's config folder. The certificate must contain private key.
@@ -1438,7 +1447,7 @@
-
Specify a PKCS #12 certificate (.pfx) file path on the server. The path can be relative to the DNS server's config folder. The certificate must contain private key.
+
Specify a PKCS #12 certificate (.pfx or .p12) file path on the server. The path can be relative to the DNS server's config folder. The certificate must contain private key.
@@ -1618,7 +1627,7 @@ Enable Serve Stale
-
Enable the Serve Stale feature to improve resiliency by using expired or stale records in cache when the DNS server is unable to reach the upstream or authoritative name servers.
+
Enable the Serve Stale feature to improve resiliency by using expired or stale records in cache to respond when the DNS server is unable to reach the upstream or authoritative name servers to refresh the expired records before the Max Wait Time configured below.
@@ -1630,6 +1639,33 @@
The TTL value in seconds which should be used for cached records that are expired. When the serve stale TTL too expires for a stale record, it gets removed from the cache. Recommended value is between 1-3 days and maximum supported value is 7 days.
+ +
+ +
+ + seconds (valid range 0-300; recommended 30) +
+
The TTL value in seconds which should be used for the records in a stale response. This is the TTL value that the client will be using to cache the stale records.
+
+ +
+ +
+ + seconds (valid range 10-900; recommended 30) +
+
The TTL value in seconds which should be used to reset the stale record's TTL value in the cache when the resolver fails to refresh the data. The TTL reset causes the stale records to become valid again so that they can be used to serve requests normally. This reset effectively prevents the resolver from attempting to frequently update the stale records.
+
+ +
+ +
+ + milliseconds (valid range 0-1800; default 1800) +
+
The time in milliseconds that the DNS server must wait for the resolver before serving stale records from the cache. Lower value will ensure faster response at the expense of not getting updated data from the upstream. Setting value to 0 will instantly return stale answer without waiting for the resolver to fetch updates from the upstream.
+
@@ -1806,8 +1842,6 @@ - - @@ -1924,7 +1958,7 @@
Enter IP addresses, network addresses or domain names to never proxy.
-
When proxy server is configured, DNS Server will use it for all outbound network requests.
+
Note! When proxy server is configured, DNS Server will use it for all outbound network requests.
@@ -2054,7 +2088,8 @@
-
Forwarders are DNS servers which this DNS Server should use to resolve recursive queries. If no forwarders are configured then this DNS server will use preconfigured ROOT SERVERS to perform recursive resolution. To force DNS-over-HTTPS/3, use h3 URL scheme instead of https.
+
Forwarders are upstream DNS servers which this DNS Server should use to resolve recursive queries. When more than one forwarders are configured, the DNS server will randomly select one or more forwarders (as per forwarder concurrency) to query and use the fastest response it receives from anyone of them. If none of the randomly selected forwarders respond in time then the ones left are tried before giving up. If no forwarders are configured then the DNS server will use preconfigured ROOT SERVERS to perform recursive resolution.
+
Note! To force DNS-over-HTTPS/3, use h3 URL scheme instead of https.
Help: Configuring DNS Server For Privacy & Security
Help: Configuring DNS-over-QUIC and HTTPS/3 For Technitium DNS Server
@@ -2988,7 +3023,7 @@

Source code available under GNU General Public License v3.0 on  GitHub

What's New?

-

Read the change log to know whats new in this release.

+

Read the change log to know what's new in this release.

API Documentation

The DNS server HTTP API allows any 3rd party app or script to configure the DNS server. The HTTP API is used by this web console and thus all the actions that this web console does can be performed via the API. Read the HTTP API documentation for complete details.

@@ -3563,6 +3598,7 @@ ns1.example.com ([2001:db8::]) + @@ -3749,6 +3785,21 @@ ns1.example.com ([2001:db8::]) + + +