Skip to content

AdGuard Home v0.100.2
Compare
Choose a tag to compare
@ameshkov ameshkov released this 18 Dec 14:22
v0.100.2
b54bf94

We must apologize to everyone who expected v1.0 to come after v0.99 for tricking y'all a little bit. 😔 Please let the multiple new features and other useful changes be the saving Grace for poor v0.100. And there's a lot of new stuff, just look at it:

Blocking disguised trackers: #1185

You might have heard the news about third-party trackers disguised as first-party by using CNAME (or even A/AAAA) DNS records. This is not a problem for AdGuard Home now! 💪It checks if DNS responses contain any blacklisted IP addresses or CNAME records, and blocks DNS queries if there are any.

Improved Browsing Security and Parental Control services performance: #525

AdGuard Home provides an option to use AdGuard's own website rating web services to check if a domain is malicious or has adult content. The problem with these web services was that their performance was not ideal. Now we use AdGuard DNS servers instead, and the situation has greatly improved. Note that we're still using the privacy-preserving protocol that does not expose domain names to the web services. 😇

Fine-grained client settings: #821 #809

Here go two long-awaited features.

First of all, it is now possible to configure different DNS servers for different clients. For instance, you might want your kids to use a DNS server with some additional protection, and choose something less restrictive for yourself. 😏 This is not a problem anymore!

Second, a "client" may now have multiple identifiers: IP, MAC addresses or CIDR ranges. Why would you need that? For instance, a person may be using different devices and would like to have the same config for all of them. Also, this is an easy way to create "client groups" (Kids, Family, Guests, etc).

image

DNS server configuration: #1165

Here's what's included here.

  1. Blocking mode. You can now choose among three options: NXDOMAIN, null IP, custom IP address. With the latter, you can now use something like pixelserv-tls to block DNS queries.
  2. An option to send EDNS Client Subnet: #1091. This might be useful to those who run a public AdGuard Home server.
  3. An option to configure the rate limit. It was always possible via the configuration file, but now it's also exposed to the UI.

image

Cloudflare is not the default resolver anymore: #1116

It couldn't make it till the official v1.0 release... 🥺 While we have nothing against this resolver per se, it may be not working good enough with some devices. You can learn more about why we did this here.

Breaking changes in the API

There are some incompatible changes in the API in this version. 🚨 Please read the changelog to learn more:
https://github.com/AdguardTeam/AdGuardHome/blob/master/openapi/CHANGELOG.md

Other changes and bug fixes

  • [Changed] Update to Go v1.13: #1041
  • [Added] Extract the client's IP address from HTTP headers in case of a reverse proxy: #1220
  • [Added] Add Norwegian language to AdGuard Home: #1174
  • [Added] An option to reset DHCP configuration: #1024
  • [Fixed] Fix the order of modules initialization on startup: #1212
  • [Fixed] 502 error after the AGH update: #1186
  • [Fixed] DNS Settings description text is inaccurate: #1022
  • [Fixed] Client name couldn't be resolved via rDNS if client has 2 names: #1230
  • [Fixed] DHCP server ignores static assignment: #1005
  • [Fixed] IPv6 address could not be used as client identifiers: #1075
  • [Fixed] No paging in the DHCP static leases table: #1197
  • [Fixed] User session issues: #1006 #1106 #1196
  • [Fixed] Panic when requesting query log data: #1194
Assets 12
Loading