chore(deps): update adguard/adguardhome docker tag to v0.107.71

[renovate]

This PR contains the following updates:

Package	Update	Change
adguard/adguardhome (source)	patch	v0.107.65 → v0.107.71

---

Release Notes

AdguardTeam/AdGuardHome (adguard/adguardhome)

v0.107.71

Compare Source

See also the v0.107.71 GitHub milestone.

Changed

• Stale records in optimistic DNS cache now have an upper age limit controlled by dns.cache_optimistic_max_age. The default value is 12 hours.

• TTL for stale answers from optimistic DNS cache is now controlled by dns.cache_optimistic_answer_ttl. The default value is 30 seconds.

Configuration changes

In this release, the schema version has changed from 31 to 32.

• Added a new string fields dns.cache_optimistic_answer_ttl and dns.cache_optimistic_max_age.

  # BEFORE:
  'dns':
    'cache_enabled': true
    'cache_optimistic': true
    # …
  
  # AFTER:
  'dns':
    'cache_enabled': true
    'cache_optimistic': true
    'cache_optimistic_answer_ttl': '30s'
    'cache_optimistic_max_age': '12h'
    # …
    ```
  
  To roll back this change, set the `schema_version` back to `31`.

Fixed

• Optimistic DNS cache not working (#​8148).

v0.107.70

Compare Source

See also the v0.107.70 GitHub milestone.

Security

• Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.25.5.

Added

• New field "start_time" in the GET /control/status response.

Changed

• Stale records in optimistic DNS cache now have an upper age limit of 12 hours.

• New blocked services UI.

Fixed

• Generated mobileconfig could not be installed on macOS 26.1.

v0.107.69

Compare Source

See also the v0.107.69 GitHub milestone.

Changed

• Node.js 24 is now used to build the frontend.

Deprecated

• Node.js 20 and 22 support.

Fixed

• DHCP settings could not be saved (#​8075).

• DNS Rewrite edit modal did not populate with the correct values (#​8072).

Removed

• The outdated querylog anonymization script.

v0.107.68

Compare Source

See also the v0.107.68 GitHub milestone.

Security

• Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.25.3.

Added

• New DNS rewrite settings endpoints GET /control/rewrite/settings and PUT /control/rewrite/settings/update (#​1765). See openapi/openapi.yaml for details.

• New fields "groups" and "group_id" added to the HTTP API (GET /control/blocked_services/all). See openapi/openapi.yaml for the full description.

Changed

• POST /control/rewrite/add and PUT /control/rewrite/update now accept the optional field "enabled" (#​1765). See openapi/openapi.yaml for details.

Configuration changes

In this release, the schema version has changed from 30 to 31.

• Added a new boolean field filtering.rewrites_enabled to globally enable/disable DNS rewrites.

• Added a new boolean field enabled for each entry in filtering.rewrites to toggle individual rewrites.

  # BEFORE:
  'filtering':
    'rewrites':
      - 'domain': test.example
        'answer': 192.0.2.0
    # …
  
  # AFTER:
  'filtering':
    'rewrites_enabled': true
    'rewrites':
      - 'domain': test.example
        'answer': 192.0.2.0
        'enabled': true
    # …

  To roll back this change, set schema_version back to 30.

v0.107.67

Compare Source

See also the v0.107.67 GitHub milestone.

Added

• The HaGeZi's DNS Rebind Protection filter for protecting against DNS rebinding attacks (#​102).

• Support for configuring the suggested default HTTP port for the installation wizard via the ADGUARD_HOME_DEFAULT_WEB_PORT environment variable (useful for vendors).

Changed

• Optimized matching of filtering rules.

Fixed

• Excessive configuration file overwrites when visiting the Web UI and a non-empty language is set.

• Lowered the severity of log messages for failed deletion of old filter files (#​7964).

v0.107.66

Compare Source

See also the v0.107.66 GitHub milestone.

Security

• Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.25.1.

Changed

• Our snap package now uses the core24 image as its base.

• Outgoing HTTP requests now use the User-Agent header AdGuardHome/v0.107.66 (where v0.107.66 is the current version) instead of Go-http-client/1.1 (#​7979).

Fixed

• Authentication errors in the Web UI when AdGuard Home is behind a proxy that sets Basic Auth headers (#​7987).

• The HTTP API GET /control/profile endpoint failing when no users were configured (#​7985).

• Missing warning on the Encryption Settings page when using a certificate without an IP address.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.