You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Adguard DNS uses an anonymized subnet for ECS which may be inaccurate in some countries.
For example in Vietnam, if Adguard uses an subnet in HCM which tells the upstream DNS server to prefer to return servers near HCM/Singapore, while servers in HN/Hongkong are better if you are in Hanoi. (map: https://www.mapcustomizer.com/map/hn-hcm-hk-sgp)
Proposed solution
Could you make this optional, something like this:
(captured from nextDNS's website)
enable anonymized ECS -> use an anonymized subnet chosen by Adguard as currently.
disable -> use the real subnet of the user eg. 14.226.xx.0/24
or whatever is set by the user in e.g. AdguardHome, dnsproxy...
The text was updated successfully, but these errors were encountered:
Note, that NextDNS does not send your real ECS, it tries to anonymize it using the way that's very similar to ours.
We use different approaches to improve cache efficiency though. They only enable ECS for a "whitelist" of domains, and we use a limited set of AS numbers instead. We'll publish an article with a more detailed explanation.
Anyways, I suggest you trying again, we made some improvements recently.
The last issue to solve with our anonymization algorithm is big providers in large countries, once we solve it everyone will be happy.
Issue Details
Currently Adguard DNS uses an anonymized subnet for ECS which may be inaccurate in some countries.
For example in Vietnam, if Adguard uses an subnet in HCM which tells the upstream DNS server to prefer to return servers near HCM/Singapore, while servers in HN/Hongkong are better if you are in Hanoi. (map: https://www.mapcustomizer.com/map/hn-hcm-hk-sgp)
Proposed solution
Could you make this optional, something like this:
![Screenshot 2023-08-12 102934](https://private-user-images.githubusercontent.com/11857205/260197512-0f5a593c-f49e-40a6-9c10-3331f484893d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjYxNzI5NjIsIm5iZiI6MTcyNjE3MjY2MiwicGF0aCI6Ii8xMTg1NzIwNS8yNjAxOTc1MTItMGY1YTU5M2MtZjQ5ZS00MGE2LTljMTAtMzMzMWY0ODQ4OTNkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTEyVDIwMjQyMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTA4ZjRmZjk5OTM4MjAyNWQ4YzI2MDM5Nzc2MWFhNTNiNzQyMTQyMzI5ZjQyM2I0YjFhNWEyZjA1YmFkZThkYTAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.KOvKNBw4kIvvTo2qUKGeWiMlogTEjxpaY_dHuqptY2o)
(captured from nextDNS's website)
14.226.xx.0/24
The text was updated successfully, but these errors were encountered: