Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hide upstream resolver from dns query answer #110

Open
Streametch opened this issue Jul 8, 2024 · 2 comments
Open

Hide upstream resolver from dns query answer #110

Streametch opened this issue Jul 8, 2024 · 2 comments

Comments

@Streametch
Copy link

Hello,
Some services, like anti spam Rbl lists, detect dns resolver public or not. If knot-resolver using forward rules to public resolvers like google/cloudflare then access to antismap RBL's may fails. Is any way how to excludes RBL's domains from forwarding, or maybe some tricks how to hide or replace upstream resolvers from query answer?

@vcunat
Copy link
Member

vcunat commented Jul 10, 2024

In 5.x version you can use the .PASS action to skip over all further rules (including forwarding rules). So if you put this early enough and conditioned to trigger only on some QNAME subtrees, I believe it will work.

In 6.x this isn't doable in a reasonable way yet, I think.

@vcunat
Copy link
Member

vcunat commented Jul 11, 2024

6.x: a different forwarding specification as exception should work there, so if you e.g. find a resolver that's not so well known or if you have another non-forwarding instance...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants