First of all, thank you for this amazing tool. routedns is beautifully designed and extremely powerful.
I would like to ask how I can implement domain-based DNS routing where different domain groups are resolved using different protocols and resolvers.
My goal is:
• Some specific domains should be resolved over UDP/TCP on port 53 using a specific resolver.
• Some other specific domains should be resolved via DoH using a specific DoH endpoint.
In other words, I want DNS behavior like this:
Example:
• facebook.com, youtube.com, google.com → resolve via udp://1.1.1.1:53
• whatsapp.com, telegram.org, signal.org → resolve via DoH, e.g. https://dns.google/dns-query
So when a client queries facebook.com, it should go to the UDP/TCP resolver, but when it queries whatsapp.com, it should be resolved through the DoH endpoint.
What is the correct way to configure this kind of domain-based DNS routing in sniproxy?
Is this supported natively, or does it require a custom rule engine or an external component?
First of all, thank you for this amazing tool. routedns is beautifully designed and extremely powerful.
I would like to ask how I can implement domain-based DNS routing where different domain groups are resolved using different protocols and resolvers.
My goal is:
• Some specific domains should be resolved over UDP/TCP on port 53 using a specific resolver.
• Some other specific domains should be resolved via DoH using a specific DoH endpoint.
In other words, I want DNS behavior like this:
Example:
• facebook.com, youtube.com, google.com → resolve via udp://1.1.1.1:53
• whatsapp.com, telegram.org, signal.org → resolve via DoH, e.g. https://dns.google/dns-query
So when a client queries facebook.com, it should go to the UDP/TCP resolver, but when it queries whatsapp.com, it should be resolved through the DoH endpoint.
What is the correct way to configure this kind of domain-based DNS routing in sniproxy?
Is this supported natively, or does it require a custom rule engine or an external component?