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
What would you like us to support (In short summary)
Motivation & Background
If we add dnsmasq and systemd-resolved to must_direct, in 'binding to WAN' scenario, DNS mapping will fail because all DNS queries will bypass dae.
The best way is to refer to external-dns.md. But it is not OOTB (out-of-the-box) and is expensive to configure.
Removing them from must_direct is not the best way but just acceptable. Its disadvantage is that those local domain servers have cache and they will not always request to upstream each time, thus if some domains share the same IP, domain rules can be incorrectly matched due to incorrect mappings.
The text was updated successfully, but these errors were encountered:
What would you like us to support (In short summary)
Motivation & Background
If we add
dnsmasq
andsystemd-resolved
to must_direct, in 'binding to WAN' scenario, DNS mapping will fail because all DNS queries will bypassdae
.The best way is to refer to external-dns.md. But it is not OOTB (out-of-the-box) and is expensive to configure.
Removing them from must_direct is not the best way but just acceptable. Its disadvantage is that those local domain servers have cache and they will not always request to upstream each time, thus if some domains share the same IP, domain rules can be incorrectly matched due to incorrect mappings.
The text was updated successfully, but these errors were encountered: