Separate names with a comma.
Discussion in 'Feature Requests (AdGuard for Mac)' started by Bruno, Oct 28, 2016.
Is the DNS option on the iOS version planned to be implemented on macOS one?
No, we don't, we simply do not see much reason to do so. In which cases do you think DNS blocking in Mac would be preferrable to regular ad blocking?
For instance the Family Protection is the option that I enabled on all my iOS devices.
The regular ad blocking does not prevent what your DNS does.
And for your information I even added on my wifi setup Norton DNS address which adds an extra layer.
Do you mean iOS or Mac here? With iOS it is true, because it can't filter ads in apps otherwise; with Mac the regular adblocking is sufficient.
This is something we plan to implement in Mac version, but it will not be based on DNS blocking.
Generally, DNS blocking is not ideal, because you risk to block extra requests (for example, when the same servers are used to load both useful content and ads).
I meant with Mac. However I do not agree with you. Your iOS family DNS protection blocks more than ads. It also blocks adult websites, which is not the case with the Mac version. This is why I'm using at the present time Norton DNS is my setup: 126.96.36.199, 188.8.131.52
You can set up your DNS to block unsafe malware, phishing sites and scam sites and/or porn too.
Be assured if I want to block porn sites then I consider there is not used content.
We could incorporate it inside of Adguard. The thing is that it is pretty easy to set it up manually.
I'd advise you trying DNSCrypt OS X client:
I allows to quickly turn AG DNS on or off.
I was not aware of this tool. Also I looked at it closer. I do not think it does the same thing that your DNS on iOS.
First it is provided by OpenDNS which is far from the best DNS for me.
Also, the DNS file provided: /usr/share/dnscrypt-proxy/dnscrypt-resolvers.csv needs to be changed with the DNS you want to use.
No easy for the neophyte user...
Also, it crashes the configuration you might have done in Network Manager /etc/resolv.conf
Not cool at all!
Finally after using it I found out that the query time I had, between 20 to 25 msec increased to 325 to 1728 msec!!
The only solution I found was to set up a DNS cache to maximise the query time. Seriously? Too much pain.
I conclusion, good tool to encrypted your DNS between you and your ISP but the setup is kind of pain in the ass.
Also, it needs to be review on regular basis to make sure you have the right setup.
Thanks anyway for the tip!
The tool itself is open source and is not directly linked to opendns, so it shouldn't be a problem.
It was not that bad in my case. Although it was not good Resolvers file is updated automatically, but you may need to restart/enable/disable it a few times before it is finally done