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

AdGuard DNS appears to be less favorable for VPN users. #787

Open
lukyduck5 opened this issue Jun 17, 2024 · 1 comment
Open

AdGuard DNS appears to be less favorable for VPN users. #787

lukyduck5 opened this issue Jun 17, 2024 · 1 comment

Comments

@lukyduck5
Copy link

lukyduck5 commented Jun 17, 2024

Issue Details

According to an AdGuard blog post and my personal testing, ECS seems to be optimized only for large ISPs and may not be optimized for hosting providers commonly used by AWS, Linode, and VPN companies like CDN77 and M247. Therefore, it's common to see instances where, for example, I use a Tokyo EC2 instance, but ECS may be targeting AWS' European/North American segments.

Proposed solution

I personally believe clients should have the option to choose whether to use ECS. Personally, I lean towards not using ECS. In my tests with 1.1.1.1 and 9.9.9.9, I found the DNS resolution results to be satisfactory as well.

Alternative solution

Perhaps we can take a cue from Controld; their ECS points to their own DNS server segments. For example, if I use a Tokyo M247 server, Controld's ECS would point to NetActuate's Tokyo segment.
Screenshot_20240617_175744

@pictosun
Copy link

Bit ECS isn't meant for doing it like ControlD is doing, or am I wrong?

As far as I understand ECS should do it that way AdGuard and NextDNS are doing...

What happens, when ControlD doesn't have a server within a country/region - then it's getting worse.

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

2 participants