9/9/21, 7:47 AM AdGuard Home

DNS settings

Enter one server address per line. Learn more about configuring upstream DNS servers. Here is a list of known DNS providers to choose from.

https://1.1.1.1/dns-query

https://1.0.0.1/dns-query

Load-balancing
Query one upstream server at a time. AdGuard Home will use the weighted random algorithm to pick the server so that the fastest server is used more
often.

Parallel requests
Use parallel queries to speed up resolving by querying all upstream servers simultaneously.

Fastest IP address
Query all DNS servers and return the fastest IP address among all responses. This slows down DNS queries as AdGuard Home has to wait for responses
from all DNS servers, but improves the overall connectivity.

Examples:
1. 94.140.14.140 - regular DNS (over UDP)

2. tls://dns-unfiltered.adguard.com – encrypted DNS-over-TLS

3. https://dns-unfiltered.adguard.com/dns-query – encrypted DNS-over-HTTPS

4. quic://dns-unfiltered.adguard.com:784 – encrypted DNS-over-QUIC (experimental)

5. tcp://94.140.14.140 – regular DNS (over TCP)

6. sdns://... – you can use DNS Stamps for DNSCrypt or DNS-over-HTTPS resolvers

7. [/example.local/]94.140.14.140 – You can specify a DNS upstream for the specific domain(s)

8. # comment – You can specify a comment

Bootstrap DNS servers

Bootstrap DNS servers are used to resolve IP addresses of the DoH/DoT resolvers you specify as upstreams.

1.1.1.1:53

Private DNS servers

The DNS servers that AdGuard Home uses for local PTR queries. These servers are used to resolve the hostnames of clients with private IP addresses, for example "192.168.12.34",
using rDNS. If not set, AdGuard Home uses the default DNS resolvers of your OS.

Enter one server address per line

Enable reverse resolving of clients' IP addresses

If enabled, AdGuard Home will attempt to reversely resolve clients' IP addresses into their hostnames by sending PTR queries to corresponding resolvers (private
DNS servers for local clients, upstream server for clients with public IP addresses).

Test upstreams Apply

Rate limit
The number of requests per second allowed per client. Setting it to 0 means no limit.

https://home.nzo.se/hassio/ingress/a0d7b954_adguard 1/3
9/9/21, 7:47 AM AdGuard Home

20

Enable EDNS Client Subnet

If enabled, AdGuard Home will be sending clients' subnets to the DNS servers.

Enable DNSSEC
Set DNSSEC flag in the outcoming DNS queries and check the result (DNSSEC-enabled resolver is required)

Disable IPv6
If this feature is enabled, all DNS queries for IPv6 addresses (type AAAA) will be dropped.

Blocking mode
Default: Respond with zero IP address (0.0.0.0 for A; :: for AAAA) when blocked by Adblock-style rule; respond with the IP address specified in the rule when blocked by
/etc/hosts-style rule
REFUSED: Respond with REFUSED code
NXDOMAIN: Respond with NXDOMAIN code
Null IP: Respond with zero IP address (0.0.0.0 for A; :: for AAAA)
Custom IP: Respond with a manually set IP address

Default
REFUSED
NXDOMAIN
Null IP
Custom IP

Save

Cache size
DNS cache size (in bytes)

4194304

Override minimum TTL

Extend short time-to-live values (seconds) received from the upstream server when caching DNS responses

Enter minimum TTL (seconds)

Override maximum TTL

Set a maximum time-to-live value (seconds) for entries in the DNS cache

Enter maximum TTL (seconds)

Save

Allowed clients
A list of CIDR or IP addresses. If configured, AdGuard Home will accept requests from these IP addresses only.

Disallowed clients
A list of CIDR or IP addresses. If configured, AdGuard Home will drop requests from these IP addresses.

Disallowed domains
Don't confuse this with filters. AdGuard Home will drop DNS queries with these domains in queries' questions. Here you can specify the exact domain names, wildcards and URL
filter rules, e.g. "example.org", "*.example.org" or "||example.org^".

https://home.nzo.se/hassio/ingress/a0d7b954_adguard 2/3
9/9/21, 7:47 AM AdGuard Home

version.bind

id.server

hostname.bind

Save configuration

https://home.nzo.se/hassio/ingress/a0d7b954_adguard 3/3