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

Implement canary domain signal for Firefox #988

Closed
ameshkov opened this issue Sep 8, 2019 · 3 comments
Closed

Implement canary domain signal for Firefox #988

ameshkov opened this issue Sep 8, 2019 · 3 comments
Assignees
Milestone

Comments

@ameshkov
Copy link
Member

ameshkov commented Sep 8, 2019

DNS queries for the A and AAAA records for the domain “use-application-dns.net” must respond with NXDOMAIN rather than the IP address retrieved from the authoritative nameserver.

https://support.mozilla.org/en-US/kb/configuring-networks-disable-dns-over-https

IMPORTANT: it must be done in dnsproxy because we need this in mobile versions as well.

@ameshkov ameshkov added this to the v0.99 milestone Sep 8, 2019
adguard pushed a commit that referenced this issue Sep 12, 2019
#988

* commit '47e29f96dfb9f254babcf4763912dc5e9a07ee2a':
  + dnsforward: disable Mozilla DoH - block use-application-dns.net
@szolin szolin closed this as completed Sep 17, 2019
@hoshsadiq
Copy link

Hello @ameshkov and @szolin. In my opinion this should be a opt-in configuration option. As you said in changelog, it's not that we think CloudFlare is bad (neither that they're good for that matter), but it's about choice, so there's no need to force such as a behaviour onto users. I personally will be disabling Mozilla's DoH when it eventually hits Europe, but even so, it should be an opt-in feature.

@ghost
Copy link

ghost commented Oct 25, 2019

I think it's not important and we can have this after some months #821 then it's not necessary for let such kid(mozilla) to enjoy 😉

@ameshkov
Copy link
Member Author

@hoshsadiq AdGuard Home is a DNS filtering solution so when someone uses it, they basically explicitly state that they want to filter their DNS queries. I think that this alone already counts as opt-in.

I was also thinking about making it an opt-out feature, but here are two reasons of why not to:

  1. AG Home by itself provides encrypted DNS
  2. You can simply configure FF to use a resolver you want (and this will be a clear opt-out).

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

3 participants