Hacker News new | ask | show | jobs
by EpiphanyMachine 2721 days ago
update: They say they do not log anything, and pass no information upstream to the authoritative DNS server.

------

I didn't see anything in the announcement about logging or other privacy related questions. The FAQ also didn't list this information.

The only thing they mention about privacy is how a dns request to them is protected, but not what they do with the data.

Did I miss something?

-------

Reading their privacy policy:

>We do not collect anything for tracking purposes and take all necessary technical, administrative and physical measures to protect the information we get.

>When AdGuard DNS user tries to visit a page, our server receives following information: User’s IP-address; DNS request which contains domain name.

>The DNS request will be forwarded to a root or authoritative DNS server, but for the upstream server it looks as if this request is originated from AdGuard DNS server, there is absolutely no way for them to identify the original user. We, in our turn, do not log or save any of this information.

https://adguard.com/en/privacy/dns.html

1 comments

I suspect this really screws with the DNS tricks used by many CDNs to route requests to near-by servers. So I would not be surprised if, when using this, YouTube, Netflix, etc, get much slower.
I see the website loading speeds are affected, but I think it is worth it. This is a good stop-gap for anyone who have not setup a pi-hole just yet but at do not want to install an app or an extension in its stead.

Prior to this, I was running Intra [0] on my Android phone to route all DNS traffic to cloudflare-dns and had been pretty happy to use it in tandem with PrivacyBadger, uMatrix, and uBlockOrigin on Firefox.

Someone suggested using AdAway [1] on rooted devices and another app that does a similar trick of running a local VPN on Android through user supplied hosts file. Great alternative.

[0] https://getintra.org/

[1] https://adaway.org/

depends whether or not they're passing EDNS0 Client Subnet data to the authoritative DNS parties, and whether those parties are listening for it / trusting it.

We embed ECS data in our requests at DNSFilter to the authoritative upstreams, and we have a large global anycast network, so even if they're not accepting it, the answer is coming from a server 'nearby' the originating dns request, so CDN requests shouldn't be affected much.

That's the first thing I thought; How does this effect georouting?