personalDNSfilter FAQ

In this FAQ, the help page and at our Telegram group.
• Make sure private DNS is disabled in Android network settings
• Option "DNS proxy mode without local VPN" works only with rooted devices or with an additional app for redirecting the DNS traffic to personalDNSfilter (e.g. OpenVPN for pDNSf, Netguard, etc.)
• Option "DNS proxy mode without local VPN" on rooted device required option "root mode without local VPN" in order to work without additional app for redirecting DNS traffic
• Make sure private DNS is disabled in Android network settings
• Make sure that data saver is disabled in chrome
• For older chrome versions, asynchronous DNS needs to be disabled in chrome
• Make sure "use secure DNS" is disabled in privacy & security section in browser settings
• Reboot your phone
• In case it still is not working, stop personalDNSfilter, edit dnsfilter.conf within personalDNSfilter folder, set routeUnderlyingDNS = true
• Android’s battery optimization kills applications! Make sure battery optimization is disabled for personalDNSfilter
• In the Android settings enable "always on VPN" if personalDNSfilter is running in VPN mode (non-root) • Your Android ROM kills the personalDNSfilter service (e.g. MIUI and other heavily customized ROMs)
Those ads can't be blocked via DNS filtering, because they are loaded from the same domains/hosts as the videos or content. We can only recommend using YouTube Vanced or Newpipe. For other platforms have a look if there are any alternative clients/apps available that show the content and have an ad blocking feature.
Please do not use this Android system setting, if personalDNSfilter is running in VPN mode. Our app only interferes DNS requests, not the entire traffic. This is why your internet connection is blocked then.
• The main configuration is stored in “dnsfilter.conf” within the personalDNSfilter folder
• On Android, the personalDNSfilter folder is located within the public application folder on external storage. For most of the devices, this is "/storage/emulated/0/Android/data/dnsfilter.android/files/PersonalDNSFilter". In case you have an external SD Card, check also the corresponding folder on your SD Card
• On non-android version, the personalDNSfilter folder is created within the application work directory during initial start
• Some applications might stop working when network access to specific domains is blocked
• Option 1: On Android remove the app from blocking by white listing the application via "Advanced settings → App whitelist"
• Option 2: In case you know the blocked domain causing the trouble, you can whitelist the domain via an entry into additionalHosts.txt (on Android option “Configure additional hosts”) or via selection from live log
On Android remove the app from blocking by whitelisting the application via "Advanced settings → App whitelist"
• Via the Android UI you can select entries directly from the live log and chose "Add filter" from context menu
• Via an entry into additionalHosts.txt (on Android option "Configure additional hosts")
• Via the Android UI, you can select entries directly from the live log and chose "Remove filter" from context menu
• Via an entry into additionalHosts.txt (on Android option "Configure additional hosts")
Yes! Check the "full package" at the personalDNSfilter web page.
Just unzip the full package and see the readme file for next steps. If you still need help just ask at our Telegram group.
• In case you do not need an UI, just edit dnsfilter.conf configuration file or additionalHosts.txt within the application folder
• In case you need an UI, you can use the Android application to manage your non-android instance remotely (for details see "how-to-remote-control" information within the full package
• The backup is created in a subfolder of the application folder. It is in the nature of Android that this folder is deleted, when the application is removed
• In case you need to preserve the configuration, please create a copy of the personalDNSfilter folder yourself by navigating to "/storage/emulated/0/Android/data/dnsfilter.android/files/PersonalDNSFilter" using a file manager
No. We can't and don't collect or sell user data. The VPN used for personalDNSfilter is only locally. No data is sent to us.
No. personalDNSfilter is not a VPN application that connects to a server to hide your IP. The local VPN is only used to filter the DNS requests.
No, it does not in any way. personalDNSfilter has only access to the app data folder on your storage. This is needed for the configuration files of our app.
No, personalDNSfilter does not filter on an advanced content level, it blocks DNS requests. You can not use filters with advanced syntax.
No. personalDNSfilter works even great if millions of blocked hosts are added. It won't slow down anything.
personalDNSfilter will not slow down your system. The RAM consumption by the app is minimal (just a few MB). Your battery will not be drained by personalDNSfilter and you will save mobile data by blocking hosts.
• Lock personalDNSfilter in RAM
• Use app pinning
• Enable autostart for the app in MIUI settings
• Disable restrictions for the app in MIUI settings
• Make sure battery optimization is disabled for personalDNSfilter
• In the Android settings enable "always on VPN" if personalDNSfilter is running in VPN mode (non-root)
CNAME cloaking is a method to disguise a third-party domain as part of the first-party domain. It allows the third-party to track your internet activity as a first-party. CNAME cloaking gives third-party trackers a chance to trick ad-blockers who want to prevent tracking. personalDNSfilter protects you from that method, if you enable CNAME cloaking protection.