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.

Sign up for GitHub

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

Jump to bottom

Update OpenDNS options #3428

Closed
TPS opened this issue May 5, 2020 · 2 comments
Closed

Update OpenDNS options #3428

TPS opened this issue May 5, 2020 · 2 comments
Assignees
@admitrevskiy
Labels
Resolution: Done Status: Closed UI Version: AdGuard v3.5 beta 1 Version: AdGuard v3.5
Milestone
3.5

Comments

@TPS
Copy link
Contributor

TPS commented May 5, 2020 •
edited

Problem Description

OpenDNS (along w/ FamilyShield version) support needs to be updated in DNS Filtering settings.

Proposed Solution

In addition to DNSCrypt, expose DoH. Also, deploy DNSSec, whatever method is chosen to connect to OpenDNS.
@adguard-bot adguard-bot added this to the 3.5 milestone May 15, 2020
@TPS
Copy link
Contributor Author

TPS commented Aug 2, 2020

Just found this implemented in v3.5ƞ5 (32). Thanks!

But it seems notably, annoyingly slower than DNSCrypt. Is that why it's the last option listed? Is there anything y'all can do to make it @ least equally-perform DNSCrypt?

@TPS
Copy link
Contributor Author

TPS commented Aug 22, 2021 •
edited

@admitrevskiy I see DNSSEC is deployable since #3859. How do I tell whether it's active for a given resolver, e.g., this 1? I show nothing on the settings page that specifies that:

Screenshot_20210822-084134 (1).png

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@admitrevskiy admitrevskiy

Labels
Resolution: Done Status: Closed UI Version: AdGuard v3.5 beta 1 Version: AdGuard v3.5
Projects
None yet
Milestone
3.5
Development

No branches or pull requests
3 participants
@TPS @adguard-bot @admitrevskiy