AdguardTeam/AdGuardHome v0.107.0-b.6

AdGuard Home v0.107.0-b.6

on GitHub

Changes compared to the previous beta, v0.107.0-b.5. See CHANGELOG.md for all changes.

Trusted proxies (#2799)

When a client is located behind an HTTP-proxy (e.g. NGINX), normally AdGuard Home wouldn't trust standard headers (like X-Real-IP) and would display the proxy's IP address as the client's.

Now you have an option to configure a list of trusted proxies. IP headers from IP networks (CIDR) and IP addresses present in this list will be considered trusted. For the clients hidden behind an HTTP-proxy not from the “trusted” list the behavior will remain the same and the proxy's IP will be used.

By default, only the local loopback will be trusted. You need to manually add all proxies you trust to the list if you want to see real IP addresses next to your clients in the query log, and make sure that your proxies don't pass random headers to AdGuard Home.

Added

• Static IP address detection on FreeBSD (#3289).

Changed

• DNS-over-HTTPS queries that come from HTTP proxies in the trusted_proxies list now use the real IP address of the client instead of the address of the proxy (#2799).

Fixed

• Incomplete HTTP response for static IP address.
• DNSCrypt queries weren't appearing in query log (#3372).
• Wrong IP address for proxied DNS-over-HTTPS queries (#2799).