AdguardTeam / AdGuardDNS

Public DNS resolver that protects you from ad trackers
https://adguard-dns.io/
GNU Affero General Public License v3.0
744 stars 61 forks source link

Improved EDNS Client Subnet #659

Closed ameshkov closed 5 months ago

ameshkov commented 10 months ago

Issue Details

Currently, AdGuard DNS uses a random subnet from the same ASN where the user comes from.

This provides good enough precision for small AS, but large AS (Comcast, China Mobile, etc) need better granularity.

Proposed solution

In order to achieve better quality we should take "country" and "subdivision" into account alongside the ASN itself.

Internal task ID: AGDNS-1622

Alternative solution

No response

trmdi commented 5 months ago

Hello, is there any update on this? This would be a big improvement that benefits many users.

ameshkov commented 5 months ago

It has been done already, we just haven't announced it publicly. I explained the details on the last DNS OARC: https://www.youtube.com/watch?v=YWWJKvtX7vQ

gpodder770 commented 5 months ago

It has been done already, we just haven't announced it publicly. I explained the details on the last DNS OARC: https://www.youtube.com/watch?v=YWWJKvtX7vQ

Thanks, came back to try my personal sub again after seeing your comment. After trying for two days, I can say this really improved the speed. The tiktok you mentioned in the video was reported by me and seems to be fixed. I get 15-17 ping now instead of 200+ before the change. Furthermore, it seems facebook and instagram which uses cdn also seems to more faster now and lower ping like tiktok. Really appreciate for the changes.

ameshkov commented 5 months ago

@gpodder770 thanks, I am happy to see that this approach actually works. It's not yet finalized and only enabled for a select few countries, we may need to come up with "subdivision" approach for other countries too (see #729)

ameshkov commented 5 months ago

UPD: Official announcement is ready: https://adguard-dns.io/en/blog/privacy-friendly-edns-client-subnet.html