Update Adguard instructions for v4.0

Starting with v4.0 of the Adguard add-on, Adguard is no longer listening for DNS requests on `172.30.32.1`. You must now refer to the LAN address of HomeAssistant instead. 

I also added an explainer note for users upgrading a previously working configuration. I'm not certain if this is the right place for that but thought it should be published somewhere. Perhaps that should just be published to the changelog of this addon?
This commit is contained in:
mdegat01 2021-03-14 14:24:09 -04:00 committed by Mike Degatano
parent 5c5888d934
commit e6f8ce019d

View file

@ -113,10 +113,14 @@ A list of DNS servers used by the add-on and the configuration generated for
the clients. This configuration option is optional, and if no DNS servers are the clients. This configuration option is optional, and if no DNS servers are
set, it will use the built-in DNS server from Hass.io. set, it will use the built-in DNS server from Hass.io.
**If you are running the [AdGuard][adguard] add-on, **If you are running the [AdGuard][adguard] add-on, you can add the LAN address
you can add `172.30.32.1` as a DNS IP address in the list.** This will cause your of HomeAssistant as a DNS IP address in the list.** This will cause your clients
clients to use those. What this does, it effectively making your clients to use those. What this does, it effectively making your clients to have
to have ad-filtering (e.g., your mobile phone), while not at home. ad-filtering (e.g., your mobile phone), while not at home.
*Note: This used to recommend adding `172.30.32.1` as the IP address for Adguard.
Starting in v4.0.0 of that add-on that won't work anymore, you'll need to use
the LAN address. You will also need to update any previously configured clients.
### Option: `server.private_key` _(optional)_ ### Option: `server.private_key` _(optional)_