Differences

This shows you the differences between two versions of the page.

--- advanced-dhcpdns [2023/04/25 14:28] – rs232
+++ advanced-dhcpdns [2023/04/29 21:06] – [DHCP Client (WAN)] -clarity, condense hogwild
@@ Line 1: / Line 1: @@
 ====== DHCP/DNS/TFTP ======
-The Advanced / DHCP/DNS page allows you to configure advanced settings for the DHCP and DNS services for both LAN and WAN. Most of this functionality is provided by [[https://thekelleys.org.uk/|dnsmasq]].
+The DHCP/DNS/TFTP menu allows you to configure advanced settings for the DHCP, DNS and TFTP services for both the LAN and WAN. Most of this functionality is provided by [[https://thekelleys.org.uk/|dnsmasq]].
 ===== DHCP Client (WAN) =====
@@ Line 10: / Line 12: @@
 {{:pasted:20220119-170756.png}}\\  \\
-**Enable DNSSEC support: ** DNSSEC is a way to secure DNS by introducing authentication for DNS servers. This prevents DNS hacking and poisoning. To make it backward compatible with traditional DNS, there is no encryption. If the authoritative DNS server is DNSSEC-enabled, enabling DNSSEC ensure that queries you make are answered by that authoritative DNS server, and not an imposter. Enable this if your chosen DNS server supports it for enhanced security.
+**Enable DNSSEC support: ** DNSSEC is a way to secure DNS by introducing authentication for DNS servers. This prevents DNS hacking and poisoning. DNSSEC is not encrypted, to keep it backward-compatible with traditional DNS. If the authoritative DNS server is DNSSEC-enabled, enabling DNSSEC ensures your DNS queries are answered by that authoritative DNS server, and not an imposter. Enable this if your chosen DNS server supports it for enhanced security.
-**Use dnscrypt-proxy:  **DNSCrypt works to encrypt DNS resolution. When a DNSCrypt-enabled server is chosen, a unique key pair is generated and regenerated every hour. Queries are then encrypted using the generated key pair before they are sent to the server, usually on TCP port 443. The reply is similarly encrypted. Checking //Use dnscrypt-proxy// enables FreshTomato' built-in dnscrypt proxy client. The dnscrypt module and Stubby cannot both be used at the same time.
+**Use dnscrypt-proxy:  **DNSCrypt works to encrypt DNS resolution. When a DNSCrypt-enabled server is chosen, a unique key pair is generated and regenerated every hour. Queries are then encrypted using the generated key pair before being sent to the server, usually on TCP port 443. The reply is similarly encrypted. Checking //Use dnscrypt-proxy// enables FreshTomato's built-in dnscrypt proxy client. The dnscrypt module and Stubby cannot both be used at the same time.
+ \\
 When dnscrypt-proxy is checked, the following options/fields are revealed:
-  * Ephemeral Keys - If checked, a new key pair is generated for each DNS query. Use with care, this is very cpu-intensive. It may slow DNS resolution. \\
+  * Ephemeral Keys - If checked, a new key pair is generated for each DNS query. Use with care, as this is very cpu-intensive. It may slow DNS resolution.
   * Manual Entry - If enabled, 3 more fields are displayed:
     * Resolver Address - The IP address of the dnscrypt-enabled DNS server, for example 1.2.3.4;
@@ Line 22: / Line 26: @@
     * Provider Public Key - A public key provided by the DNSCRYPT-enabled DNS provider used to generate a valid key pair \\ e.g. 0000:1111:2222:3333:4444:5555:6666:7777:8888:9999:AAAA:BBBB:CCCC:DDDD:EEEE:FFFF
   * Resolver - This dropdown list currently contains about 200 DNS servers. Some support DNSSEC. Some don't log queries. Some are filtered. To help you choose a DNSCrypt DNS provider, import the file /etc/dnscrypt-resolvers.csv in a spreadsheet. Once chosen, the server's IP address, provider name, and public key can be extracted from that file.
-  * Priority - Leave this at //no-resolv// to prevent DNS leaks!  This should never be a choice when using DNSCRYPT. To prevent leaks, also enable //Intercept DNS port// on this page.
+  * Priority - Leave this at //no-resolv// to prevent DNS leaks!  This should never be a choice when using DNSCRYPT. To prevent leaks, also enable //Intercept DNS port//.
-  * Local Port - Specifies the port on which dnscrypt-proxy communicates with FreshTomato's DNS. Leave this at 40 unless you know why to change it. Do NOT set it to 53, it might create a loop.
+  * Local Port - Specifies the port on which dnscrypt-proxy communicates with FreshTomato DNS. It is recommended that you leave this at 40 unless you know why you're changing it. Do NOT set it to 53, or it might create a loop.
-  * Log Level - This sets the level of messages logged in syslog (when activated).
+  * Log Level - When enabled, this sets the level of messages logged to the system log.
 **Use Stubby (DNS-over-TLS):** This enhances DNS privacy. Checking this enables Stubby, a DNS Stub resolver. DNS over TLS (or "DoT") sends DNS queries over a secure connection, encrypted with TLS. TLS is the same technology that encrypts secure Web traffic. This prevents third parties from seeing your DNS queries.
+ \\
 When Stubby is enabled some extra options are appearing on your configuration:
@@ Line 32: / Line 38: @@
 {{:pasted:20220420-181042.png}}
-** Upstream resolvers:** You can specify here the upstream servers responsible to perform the actual name resolution.
+ \\
-** Priority:**
+**Upstream resolvers:** Here, you can specify the upstream servers responsible for perform the actual name resolution.
-  * Strict-Order = prefer Stubby but if this is experiencing issue fail back to "other way of resolve names" e.g. standard DNS resolution
-  * No-Resolv = If Stubby fails or has issue you will want DNS resolution not to be failed back anywhere. A.k.a. Stubby or nothing.
-  * None = This option adds stubby as a resolution method for the build in dnsmasq. Note this doesn't guarantee encryption by itself.
-** Local Port:** The port number where Stubby is serving clients. Also note the only client for Stubby will actually be dnsmasq and this latter serves the end clients.
+**Priority:**
-** Log Level:** Define here the log verbosity needed.
+  * Strict-Order:  Stubby is tried first, but if it experiences issues, fallback to other methods of name resolution, such as standard DNS.
+  * No-Resolv:  If Stubby fails or has issues, there will be no fallback to other DNS resolution methods anywhere.
+  * None:  This adds stubby as a resolution method for the built-in dnsmasq. This alone does not guarantee.
-** Force TLS1.3:** Impose the usage of the latest TLS version for encryption (must be supported by the upstream).
+**Local Port:** The port number on which Stubby will serve clients. Note that dnsmasq will be the only client for Stubby. It is dnsmasq that serves clients.
-**WINS (for DHCP):** Here, you can specify the IP address of a WINS Server which will be given to DHCP clients. This does NOT actually enable the WINS service. FreshTomato's WINS Server function is enabled on the //USB and NAS/[[:nas-samba|File Sharing]]// menu.
+**Log Level:** Allows you to choose what level of details is written in log entries.
-Windows Internet Name Service (WINS) is a legacy name registration and resolution service which maps computer NetBIOS names to IP addresses. Officially, WINS is outdated and largely obsolete. DNS was supposed to have replaced WINS functionality. However, Microsoft has not officially deprecated WINS. WINS may still be necessary for some Windows LAN browsing functions, especially on old Windows versions.
+**Force TLS1.3:**  Enforces usage of the latest TLS version for encryption. This must be supported upstream.
+**WINS (for DHCP):** Here you specify the IP address of a WINS Server that will be given to DHCP clients. This does NOT actually enable the WINS service. FreshTomato's WINS Server function is enabled on the //[[:nas-samba|File Sharing]]// menu.
+Windows Internet Name Service (WINS) is a legacy name registration and resolution service that maps computer NetBIOS names to IP addresses. Officially, WINS is outdated and largely obsolete. DNS was supposed to have replaced WINS functionality. However, Microsoft has not officially deprecated WINS. WINS may still be necessary for some Windows LAN browsing functions, especially on old Windows versions.
 **DHCPC Options:**  In this field you can enter custom configuration settings for the dhcp client.
@@ Line 126: / Line 135: @@
 **Enable TFTP**: Starts the dnsmasq's internal TFTP server with --tftp-no-fail enabled by default (to prevent dnsmasq issues in case e.g. TFTP root becomes unavailable).
-**TFTP root path**: Define where the TFTP root is located in the filesystem
+**TFTP root path**: Defines where the TFTP root is located in the filesystem
 **PXE on LANx (brx)**: Allows PXE (Pre Boot Execution) on one or more bridges. PXE is designed for diskless clients where a PXE client can just obtain an IP via DHCP and a TFTP location where the booting code is to be found (syslinux is for example a good application for this).
 ===== DHCP / DNS Notes =====
-  *  Do not use results from: [[https://1.1.1.1/help|https://1.1.1.1/help]]. That webpage is likely to provide wrong results. Instead, it is suggested that you use:  [[https://rootcanary.org/test.html|https://rootcanary.org/test.html]]
+  * Do not use results from: [[https://1.1.1.1/help|https://1.1.1.1/help]]. That webpage is likely to provide wrong results. Instead, it is suggested that you use: [[https://rootcanary.org/test.html|https://rootcanary.org/test.html]]
-  *  DNSSEC and DNSCrypt / Stubby complement each other.
+  * DNSSEC and DNSCrypt / Stubby complement each other.

FreshTomato Wiki

User Tools

Site Tools

Differences

Page Tools