You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a forward zone, the option forward-tls-upstream affects all forward-addrs. This is quite limiting, especially for the . zone.
Describe the desired feature
The ability to use DoT for some but not all forward addresses in the same forward zone.
One possible solution is to support an auto value for forward-tls-upstream, and infer whether to enable DoT based on each forward address. Addresses with @853 and/or #<dom> parts will use DoT, and others won't.
Potential use-case
Some secure/encrypted networks (e.g. using WireGuard) may provide an internal DNS address with fast query times. TLS is not enabled in this case since its not needed from a security PoV, and to avoid any performance overhead. But users may still want to use DoT for fallback addresses.
The text was updated successfully, but these errors were encountered:
Current behavior
In a forward zone, the option
forward-tls-upstream
affects allforward-addr
s. This is quite limiting, especially for the.
zone.Describe the desired feature
The ability to use DoT for some but not all forward addresses in the same forward zone.
One possible solution is to support an
auto
value forforward-tls-upstream
, and infer whether to enable DoT based on each forward address. Addresses with@853
and/or#<dom>
parts will use DoT, and others won't.Potential use-case
Some secure/encrypted networks (e.g. using WireGuard) may provide an internal DNS address with fast query times. TLS is not enabled in this case since its not needed from a security PoV, and to avoid any performance overhead. But users may still want to use DoT for fallback addresses.
The text was updated successfully, but these errors were encountered: