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, it understands only exact domain names. However, those who abuse public DNS servers often use random subdomain names (for instance, 03131653dot27dot91dot239dot27dot199q1w2e3rty.pku.edu.cn).
"Blocked domains" should accept wildcards
Change the help text: Don't confuse this with filters. AdGuard Home will drop DNS queries with these domains in query's question.. Add You can specify exact domain names or wildcards here, i.e. example.org or *.example.org..
The text was updated successfully, but these errors were encountered:
This AdGuard Home project is turning out incredible and the pace of development and bug fixes is fantastic. Your dev team's interaction with the open source community in particular is a wonderful thing and will help continue to make your software grow and shine.
By the way, I vaguely recall having a brief conversation with you on a security forum something like 7-10 years ago where I was telling you that it would be amazing to have an adblocking device or some sort based on OpenWrt/dnsmasq (at the time of suggesting). At the time, I believe you said it would be a great thing but rather a niche kind of tool. This is like a dream come true now. Cheers for that! :)
Currently, it understands only exact domain names. However, those who abuse public DNS servers often use random subdomain names (for instance,
03131653dot27dot91dot239dot27dot199q1w2e3rty.pku.edu.cn
).Don't confuse this with filters. AdGuard Home will drop DNS queries with these domains in query's question.
. AddYou can specify exact domain names or wildcards here, i.e. example.org or *.example.org.
.The text was updated successfully, but these errors were encountered: