Secure DNS(also known as DNS firewall & protective DNS) with ad-blocking, threat protection, and fully encryption support for enhanced privacy and security.
AdguardTeam/AdGuardHome (adguard/adguardhome)
### [`v0.107.44`](https://togithub.com/AdguardTeam/AdGuardHome/blob/HEAD/CHANGELOG.md#v010744---2024-02-06)
[Compare Source](https://togithub.com/AdguardTeam/AdGuardHome/compare/v0.107.43...v0.107.44)
See also the \[v0.107.44 GitHub milestone]\[ms-v0.107.44].
##### Added
- Timezones in the Etc/ area to the timezone list (\[[#6568](https://togithub.com/AdguardTeam/AdGuardHome/issues/6568)]).
- The schema version of the configuration file to the output of running
`AdGuardHome` (or `AdGuardHome.exe`) with `-v --version` command-line options
(\[[#6545](https://togithub.com/AdguardTeam/AdGuardHome/issues/6545)]).
- Ability to disable plain-DNS serving via UI if an encrypted protocol is
already used (\[[#1660](https://togithub.com/AdguardTeam/AdGuardHome/issues/1660)]).
##### Changed
- The bootstrapped upstream addresses are now updated according to the TTL of
the bootstrap DNS response (\[[#6321](https://togithub.com/AdguardTeam/AdGuardHome/issues/6321)]).
- Logging level of timeout errors is now `error` instead of `debug` (\[[#6574](https://togithub.com/AdguardTeam/AdGuardHome/issues/6574)]).
- The field `"upstream_mode"` in `POST /control/dns_config` and
`GET /control/dns_info` HTTP APIs now accepts `load_balance` value. Check
`openapi/CHANGELOG.md` for more details.
##### Configuration changes
In this release, the schema version has changed from 27 to 28.
- The new property `clients.persistent.*.uid`, which is a unique identifier of
the persistent client.
- The properties `dns.all_servers` and `dns.fastest_addr` were removed, their
values migrated to newly added field `dns.upstream_mode` that describes the
logic through which upstreams will be used. See also a \[Wiki
page]\[wiki-config].
```yaml
```
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 has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
v0.107.43->v0.107.44Release Notes
AdguardTeam/AdGuardHome (adguard/adguardhome)
### [`v0.107.44`](https://togithub.com/AdguardTeam/AdGuardHome/blob/HEAD/CHANGELOG.md#v010744---2024-02-06) [Compare Source](https://togithub.com/AdguardTeam/AdGuardHome/compare/v0.107.43...v0.107.44) See also the \[v0.107.44 GitHub milestone]\[ms-v0.107.44]. ##### Added - Timezones in the Etc/ area to the timezone list (\[[#6568](https://togithub.com/AdguardTeam/AdGuardHome/issues/6568)]). - The schema version of the configuration file to the output of running `AdGuardHome` (or `AdGuardHome.exe`) with `-v --version` command-line options (\[[#6545](https://togithub.com/AdguardTeam/AdGuardHome/issues/6545)]). - Ability to disable plain-DNS serving via UI if an encrypted protocol is already used (\[[#1660](https://togithub.com/AdguardTeam/AdGuardHome/issues/1660)]). ##### Changed - The bootstrapped upstream addresses are now updated according to the TTL of the bootstrap DNS response (\[[#6321](https://togithub.com/AdguardTeam/AdGuardHome/issues/6321)]). - Logging level of timeout errors is now `error` instead of `debug` (\[[#6574](https://togithub.com/AdguardTeam/AdGuardHome/issues/6574)]). - The field `"upstream_mode"` in `POST /control/dns_config` and `GET /control/dns_info` HTTP APIs now accepts `load_balance` value. Check `openapi/CHANGELOG.md` for more details. ##### Configuration changes In this release, the schema version has changed from 27 to 28. - The new property `clients.persistent.*.uid`, which is a unique identifier of the persistent client. - The properties `dns.all_servers` and `dns.fastest_addr` were removed, their values migrated to newly added field `dns.upstream_mode` that describes the logic through which upstreams will be used. See also a \[Wiki page]\[wiki-config]. ```yaml ```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.
This PR has been generated by Mend Renovate. View repository job log here.