This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
advanced-dhcpdns [2023/06/04 18:39] – [TFTP Server] hogwild | advanced-dhcpdns [2023/06/10 01:27] – [DHCP Client (WAN)] -formatting hogwild | ||
---|---|---|---|
Line 12: | Line 12: | ||
{{: | {{: | ||
- | **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 | + | **Enable DNSSEC support: ** DNSSEC is a way to secure DNS by introducing authentication for DNS servers. This prevents DNS hacking and poisoning. If the authoritative DNS server |
- | **Use dnscrypt-proxy: | + | DNSSEC is not encrypted, to keep it backward-compatible with traditional DNS. Enable this if your chosen DNS server supports it for enhanced security. |
+ | |||
+ | **Use dnscrypt-proxy: | ||
\\ When dnscrypt-proxy is checked, the following options/ | \\ When dnscrypt-proxy is checked, the following options/ | ||
Line 20: | Line 22: | ||
\\ | \\ | ||
- | * Ephemeral Keys - If checked, a new key pair is generated for each DNS query. Use this with care. It is very cpu-intensive, | + | * Ephemeral Keys - If checked, a new key pair is generated for each DNS query. Use this with care. It is very cpu-intensive, |
* Manual Entry - If enabled, 3 more fields are displayed: | * Manual Entry - If enabled, 3 more fields are displayed: | ||
Line 32: | Line 34: | ||
* Some are filtered. | * Some are filtered. | ||
- | * Priority - This should be left at // | + | * Priority - This should be left at // |
- | * Local Port - Specifies the port on which dnscrypt-proxy communicates with FreshTomato DNS. Leave this at 40 unless you're a highly advanced user. Do NOT set it to 53, as this may create a loop. | + | * Local Port - Specifies the port on which dnscrypt-proxy communicates with FreshTomato DNS. Leave this at 40 \\ unless you're a highly advanced user. Do NOT set it to 53, as doing so may create a loop. |
- | | + | |
- | **Use Stubby (DNS-over-TLS): | + | **Use Stubby (DNS-over-TLS): |
\\ | \\ | ||
Line 48: | Line 50: | ||
\\ | \\ | ||
- | **Upstream resolvers: | + | **Upstream resolvers: |
**Priority: | **Priority: | ||
- | * Strict-Order: | + | * Strict-Order |
- | * No-Resolv: | + | * No-Resolv |
- | * None: | + | * None - This adds stubby as a resolution method for dnsmasq. This alone does not guarantee. |
- | **Local Port: | + | **Local Port: |
- | **Log Level: | + | **Log Level: |
**Force TLS1.3: | **Force TLS1.3: | ||
- | **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' | + | **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' |
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. | 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. |