Hi mate,
I got a few ideas around this project, keen to hear your thoughts.
- DoQ (RFC 9250) support: I Think this one is a no brainer to add the support
dnscrypt transport: in some networks, it provides an automated way of finding the best and fastest dns server so it could be a good "auto" option if the user chooses to.
- source interface: sometimes enforcing which interface is used for outbound connections can be pivotal to prevent dns leakage especially when the underlying routing is bumpy.
- load balancing and failover for upstream DNS servers
- address blocklist (potentially malware/adware blocking)
I've tried to build my own dnsclient and lib in Go in the past (https://github.com/mosajjal/dnsclient) and I ended up realizing the best way to do this is to make it an interface compatible wrapper, and leverage already existing technologies (https://github.com/folbricht/routedns). Happy to work with you to make this a wrapper for routedns and make it compatible with the rest of the beepass project.
Hi mate,
I got a few ideas around this project, keen to hear your thoughts.
dnscrypttransport: in some networks, it provides an automated way of finding the best and fastest dns server so it could be a good "auto" option if the user chooses to.I've tried to build my own dnsclient and lib in Go in the past (https://github.com/mosajjal/dnsclient) and I ended up realizing the best way to do this is to make it an interface compatible wrapper, and leverage already existing technologies (https://github.com/folbricht/routedns). Happy to work with you to make this a wrapper for routedns and make it compatible with the rest of the
beepassproject.