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

DNS filtering: block cloaked trackers #3228

Closed
ameshkov opened this issue Nov 26, 2019 · 3 comments
Closed

DNS filtering: block cloaked trackers #3228

ameshkov opened this issue Nov 26, 2019 · 3 comments
Assignees
Milestone

Comments

@ameshkov
Copy link
Member

See the original task in the mobile API:
AdguardTeam/dnsproxy#76

@admitrevskiy
Copy link

Done. Testing instructions for QA:

  • Reinstall AG
  • Find some DNS upstream which has CNAME record for some host. For example:
dig @8.8.8.8 mail.google.com

should return CNAME record googlemail.l.google.com.

  • Enable DNS filtering and select chosen upstream
  • Add DNS filtering rule for CNAME:0.0.0.0 cname or ||cname^. For mail.google.com valid rule is ||googlemail.l.google.com^` (please note that cname record has a dot in the end. You shouldn't include this dot to the filtering rule)
  • Try to reach selected domain

Expected result:

  • Domain is blocked
  • Go to the filtering log
  • DNS request is blocked with CNAME filtering rule.

@TPS
Copy link
Contributor

TPS commented Nov 29, 2019

It seems not to be working clearly (correctly). IIUC, this is implemented in v3.3n25(166). However, my userfilter ||c. blocks m.media-amazon.com & images-na.ssl-images-amazon.com, but the log doesn't show how/why.…
Here's another: my ||trafficman unclearly blocks www.bing.com.

@admitrevskiy
Copy link

Done.
Original answer with CNAME was added to Filtering Log

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

No branches or pull requests

4 participants