Adguard Pro DNS Blacklist

U

user3

Guest
The purpose is to help people who want the old functionality of Adguard Pro's VPN. The blacklist(s) are an easy way for users to use the VPN system-wide, not only within Safari. By copy/pasting particular lists or any combination thereof into the custom DNS blacklist, that is achieved. I hope that helps clarify this for everyone.
 
U

user3

Guest
@vasily_bagirov ,
Yes, that is true. There are others, though, who, like myself, use the custom blacklist. Reasons include, but are not limited to, not wanting to use / be limited strictly to AdGuard's DNS servers, wanting the freedom to use any DNS servers they choose to use. I currently use DNS servers operated by an old contact from OpenNIC.org who left due to, and I am paraphrasing, "not liking the way in which OpenNIC's IPv6 resolution functioned". I always used this person's (d0wn) resolvers when they were still at OpenNIC. I left for reasons of neither liking nor trusting someone who was (unfortunately) voted in despite their co-current work on the Emercoin project. And now OpenNIC is peered witn Emercoin in a very insecure way that allows malocious traffic to be resolved (laundered, basically) through OpenNIC public servers onto .bit domains which are notorious for hosting malware that is nearly impossible to take down because of the way in which .bit domains have no 'true infrastructure' beyond individual servers that are nearly impossible to disrupt because of Emercoin believing they needed to own .bit name extension to compete with other cryptocurrencies (especially Bitcoin). Now they're a laughing stock of the industry and a major concern of the network security experts. I can choose, like anyone, to use any DNS servers I'd like to. For me, I use servers run by someone who I've learned to trust, who knows how to run DNS servers since that's all that they do, and who's own peering with Emercoin wasn't thrown together at the direction of someone from Emercoin. No one can piggy back off of d0wn's servers to launch bitware or bitbot attacks. d0wn's infrastructure simply won't allow it.

While I certainly didn't intend to veer off-topic when I began replying, I did because I am passionate when it comes to personal freedom, no matter the space one is inhabiting at any given moment. People use DNS Blacklists in AdGuard Pro as do I; and I know people appreciate any help they can get in setting up that list; others appreciate comparing what they use to what I use; others, like myself, prefer choosing what they block as opposed to blocking what the AdGuard DNS servers choose; while others simply prefer using any DNS servers they want to use while restoring the functioning of the local VPN that Apple forced all of you to 'officially' remove. They should know better, they stop people from doing something they used to be able to do by "upgrading" the iOS kernel and people will find a way around it, and generally do so very quickly.

If you want my work on Github to stop and be taken down, just say so. If you're uncomfortable with it, just say so. If AdGuard's legal team wants a change in the liscencing - a very strong copyleft opensource liscence that I chose in order to protect everything AdGuard stands for, as well as each project from which other lists have been "properly fixed" for use within the DNS Blacklist - they are more than welcome to talk with me on Github, throug email, or using a Jabber client. I'll post a new address I'll create after I finish this post that is more an essay on over-sharing on forums, or if you'd like to talk OTR instead of publicly for whatever reason, I'd welcome an OTR conversation over TOR. I wholeheartedly support any xmpp server that uses TOR as well as the privacy and encryption standards used by certain clients - OTR / OMEMO in tandem. (plus it'd be cool to have more people to help me help Chris in beta testing ChatSecure. I know he appreciates any bug-squashing help people give him.)

One more thing, I began a new thread for this reason: because the discussion around the topic was buried beneath hundreds of postings surrounding Apple's nerfing the VPN. And I posted a parsed URI simply becasuse I was growing tired of using non parsed URIs adding a reminder to use https:// since Github won't automatically use it and will use the less secure http:// instead when using web browsers as an interface. So I need to sleep for a day or so now... <3
 
U

user3

Guest
Hi @BobMiller and welcome!

Allow me to state the following to help clarify the answer to your question.
1. It is ultimately the choice of the user which lists to use. Each .txt file ending with the Domain Blacklist designation - DOMBL.txt - is one of many lists available for your use. Each of these has a specific purpose designated by the letters proceeding _DOMBL.txt, such as HJK (Hijacked Domains), EXP (Domains that actively host Exploits of various types), PL (Peter Lowe's List), MAL (from MalwareDomainList.com), AGS (adapted for use in the DNS Custom Blacklist from Adguard's Simplified Filterlist, a blend of filters specifically blended into one by the Adguard Developers). There are others as well, each of which contains an explaination of the list's contents prepending the list itself.
2. I would recommend the following lists to use: Adguard Simplifed* (comprised of selected domains from: English filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) but has exceptions such as googleadapis.l.google.com that serves too many ads to option out as an exception simply because it interferes with a very limited number of Apps which aren't used by most people. Any App that won't function without an active ad/tracking network is an App to avoid as there are always choices available to replace any app that is "Broken by Design". So I do not have it optioned out. It is used, just as its used in the Adguard Mobile filterlist. Peter Lowe's list & the MalwareDomainList are 2 which nicely compliment the Adguard Simplified lists. And, from my endless experimentation, Adguard Mobile (AGM_DOMBL) functions to catch mobile ad and tracking networks the Simplified List may miss. *Note: The Adguard Simplified Blacklist has some unusable chars and unusable IPs that while of no use, will not interfere with its use at all until I clean it up completely. Adguard Mobile Blacklist is a good alternative to use until the Adguard Simplified Blacklist is completely cleaned up.
3. The majority of the most annoying advertisements now affecting iOS are served by Google and Doubleclick. Google often piggybacks on doubleclick's network. pagead.l.doubleclick.net, googleadapis.l.google.com, & googleadservices.com are but 3 examples. googleadapis.l.google.com is an especially invasive ad server used in iOS Apps.
4. I also use the following domains, not (yet) posted on Github which I catagorize as ### UserDefined Domains (UD-DOMBL) -
# Appstore filters (these serve to do two things - block App images and App videos, whether the videos are the new autoplay type or not, without having to use Restriction settings) This simple combination lowers overall load time regardless of overall 'perceived' load time, i.e. true time versus deceptive time.
# App icon photos:
is1.mzstatic.com
is2.mzstatic.com
is3.mzstatic.com
is4.mzstatic.com
is5.mzstatic.com
# Appstore videos:
apptrailers.itunes.apple.com
### Apple Music filters that block iTunes Radio & iTunes Connect.
radio-services.itunes.apple.com
se2.itunes.apple.com
5. I use other personal filters according to App or web content I want blocked:
# Firefox Panels/Tiles:
tiles.services.mozilla.com
### Readdle Documents Analytics:
usage.readdle.com
 
U

user3

Guest
Ja, verwenden Sie benutzerdefinierte DNS-Blacklist. Die Domains müssen in der Liste verwendet werden. Es ist nicht genug, um die GitHub-Adresse verwenden. Eine einfache Möglichkeit, dies zu tun ist durch den Einsatz der Rohdatenansicht. Die Option "Raw" befindet sich in der oberen rechten Ecke der einzelnen Filter. Beispiel: die raw-Version des AGM_DOMBL ist @
htps://raw.githubusercontent.com/X8716e/Adguard_Pro_iOS_DNS_Blacklist/master/AGM_DOMBL.txt.

2BDB6CF3-BF63-43FA-AEFD-BD31659082C7.png
 
U

user3

Guest
Yes; I’ve chosen to recreate this within an organization instead. It’s here - https://github.com/DomainVoider. Community dedicated & community collaboration welcomed. All useful information is ultimately helpful, I hope, for AdGuard iOS development. All users of DomainVoider lists are encouraged to help out in the continual growth of AdGuard & AdGuard Pro through participating in the AdGuard’s community here & on GitHub @ https://github.com/AdguardTeam/AdguardForiOS. Thank-you for your patience everyone! DomainVoider is a labor of love. It’s time we all take back our freedom from the hands of tyrants. They think we fear them. Have they not noticed their numbers are dwindling into the mere hundreds? While ours count in the multiple billions? It’s time we re-educate them. It’s time we byte back.
 
Last edited by a moderator:
U

user3

Guest
Panatha23 said:
Just try it and works brilliant.:)
Thanks a lot.
Click to expand...
It does. If you want to use only those specific DNS addresses. Which is why I've been using by own ruleset/s since Apple stopped Adguard Pro from offering a choice of filters while allowing the user to choose which to use & which not to use in combination with any DNS servers the user chooses to use.
 
U

user3

Guest
user3 said:
Now to be hosted only on Github @

https://github.com/X8716e/Adguard_Pro_iOS_DNSDOMBL

Each file ending in _DOMBL.txt is a piece of the entire list derived from various sources.

I set this up ~1.5h ago so I'm not nearly finished committing each piece of the entire list, though I will.

View attachment 11090
Click to expand...
This now lives @ https://github.com/DomainVoider/DomainVoider.GitHub.io & will have a finished How-To guide as well as additional, need-specific rulesets added over the coming days.
 
Last edited by a moderator:
U

user3

Guest
For the sake convenience:

https://github.com/DomainVoider

All lists now separated by type in the folder 'DomainVoider'.
Be sure to read the 'Notice' in the folder 'docs' & includes all sources for the lists.
A 'How-To' is in plain sight as well as in the 'How-To' document.
Most importantly, keep those suggestions and requests coming in. They are very important to the project and to me. It shows that we, working together, can maintain the VPN functionality inherent in AdGuard Pro that Apple took from us.B5E9964C-A496-492D-87BC-12BF0F783A15.png
 
G

gecko

New Member
I like the idea of this. Good job! I've been using it in my AdGuard Pro app with modVOID and it seems to work well.
I was just wondering if I could please get more of a description of the different lists though? What exactly is the difference between modVOID and mainVOID? And what about the others? If I subscribe to modVOID, does that mean I don't need to subscribe to malVOID, or mobileVOID, or spamVOID?
 
Trumpsaduck

Trumpsaduck

Member
I keep reading as much as I can find. Trying to get an answer in these forums...is pointless. i'll help ya. Use modVoid. It's relatively small footprint, timely updates and lack of redundancy works the best. mal, mod, and testingVOID are the 3 subscriptions. The rest are custom blacklists. I'm using the beta AdGuard Pro, so your milage may vary. I notice in the 3 subs a lot of the others have been incorporated. Stick with the subscriptions.
 
You must log in or register to reply here.
Top