@ameshkov ameshkov released this Nov 27, 2018 · 83 commits to master since this release

Assets 7

📦The first serious update of AdGuard Home is ready! 📦

Initially, we wanted to include the built-in DHCP and web setup into this version, but it has been a while since we published new versions of AdGuard Home and we couldn't wait any longer. And even without those features we still have quite a lot new stuff to offer.

So what's new?

Localization

One of the key steps in making AdGuard Home what we want it to be is to make sure anyone can use it. Of course, it's essential for that purpose that AdGuard Home supports localizations. And now it does: #442.

Right out of the gates, this release brings the support of the following languages:

  • Spanish
  • French
  • Japanese
  • Portuguese
  • Russian
  • Swedish
  • Vietnamese

There's more languages to come, of course. If you want to help with AdGuard Home translations, please learn more about translating AdGuard products here: https://kb.adguard.com/en/general/adguard-translations

Here is a direct link to the AdGuard Home project: http://translate.adguard.com/collaboration/project?id=153384

Improved encrypted DNS support

We stated it many times, users' privacy and security are some of our highest priorities. The following changes (albeit to a different extent :)) follow this fundamental principle:

  • AdGuard Home now supports DNS-over-HTTPS upstream: #451
  • We fixed an annoying bug that prevented using hostnames when configuring a DNS-over-TLS upstream: #414
  • We added some examples to the upstream settings for better understanding: #453

Mitigating DNS amplification attacks

This one is a quite pressing issue actually, and those users who set up an AdGuard Home instance on a VPS are suffering from it. Unfortunately, there's no silver bullet and if you operate a public DNS server, malicious actors will eventually discover it and try to exploit. The only thing we can do is mitigate it and make it infeasible for them to use AdGuard Home instances for DNS amplification attacks: #426.

  • Rate-limiting is now enabled by default
  • By default, AdGuard Home refuses all ANY requests (which are often used for DNS amplification attacks)

The default rate-limit values are 20rps and 20kbps per client IP, but you can configure different values manually in AdGuardHome.yaml.

Other bugfixes and improvements

  • [Improvement] Family Filter: Force restricted mode on Youtube: #265
  • [Improvement] Show which filter does the rule belongs to in the query log: #371
  • [Fixed] Reboot of Raspberry PI Breaks Ad-blocking: #421
  • [Fixed] Incorrect path to the configuration file if the "-c" parameter is used: #424
  • [Fixed] Exception rule from the SDN filter does not work: #460
  • [Fixed] @@ rules won't unblock domains blocked by a hosts file: #383
  • [Fixed] Multiple mouse-over tooltips over-lapping: #439
  • [Fixed] Sort by IP address doesn't properly sort by last octet : #437
  • [Fixed] Corruption on bottom border of graphs with Edge browser : #433

Acknowledgments

Huge thanks to everybody who volunteered and contributed to this release:

Stay tuned

There's much more coming soon!

@hmage hmage released this Oct 18, 2018 · 205 commits to master since this release

Assets 7

🛠️Wow, we've reached another milestone - the first hotfix for AdGuard Home! 🛠️

It fixes a commonly-reported day1 issue: "unable to connect to port 8618", and allows running the binary when working directory is not where the binary is located. It is distributed as a standalone binary.

  • To install, download the correct archive for your operating system and architecture, extract the files and follow the installation instructions.
  • To update, stop AdGuardHome, unpack the archive, replace the binary, and start it again it.

Fixed:

  • #378 — error 127.0.0.1:8618
  • #389 — Couldn't get stats error
  • #381 — yaml config not applied
  • #377 — add docker image.

If you encounter any problems or have suggestions, feel free to open a new issue in this repo.

We will now take us some time to plan and prepare the next update. Thank you all for lots of valuable feedback we received!

@hmage hmage released this Oct 16, 2018 · 217 commits to master since this release

Assets 6

🎉We're delighted to announce the first stable release of AdGuard Home! 🎉

Don't be confused by the version number, though. It emphasizes the fact that we have A LOT of improvements planned for the future, but this version is a stable and perfectly usable product.

It is distributed as standalone binary — download the correct archive for your operating system and architecture, extract the files and follow the installation instructions.

We believe that this version is ready for production use. However, if you encounter any problems or have suggestions, feel free to open a new issue in this repo.

Official announcement on our blog.

Pre-release
Pre-release

@hmage hmage released this Aug 30, 2018 · 489 commits to master since this release

Assets 7

Hello and welcome!

We're delighted to announce open-source release of AdGuard DNS v0.1! We are distributing it as standalone binaries — download the correct archive for your operating system and architecture, extract the files and follow the README.

This is a very first release. So it's bound to be rough around the edges. Please submit any issues, problems or suggestions to GitHub issue tracker or visit the forum.

Thanks in advance,
AdGuard DNS Team.