There are three response types to choose from: Reply with a "Refused" error, Reply with an "NxDomain" error, or Redirect to a specified domain. Now you can select the response type if you’ve requested a DNS domain blocked by a DNS filtering rule. There is a new section named "Action applied to blocked DNS requests" in advanced settings. Doesn't ring a bell? Then we do suggest that you read about it and learn why DNS-over-QUIC is way better than its predecessors, DNS-over-HTTPS and DNS-over-TLS. From now on, AdGuard supports the latest version of QUIC. There were a whole lot of changes at the DNS level. Now our filters are even more flexible and powerful, capable of blocking many new things. It was updated to a new version with numerous changes and fixes. CoreLibsĬoreLibs is our main filtering engine, as you might remember. We updated CoreLibs and DNSLibs, fixed various issues along the way, and did some magic with the filtering log to make it more user-friendly. You won’t find killer features in this version but we’ve put our energy into something no less important. What's changed? For starters, we implemented advanced DNS settings, added the Finnish localization, and updated other translations. Our QA team honestly tried to break the app in various ways, but everything works great! However, you can probably find a way to do it yourself □Īnd in this case, please let us know exactly what happened and how you managed to do it. The latest release of AdGuard for Windows is a final polishing to catch as many bugs as we can.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |