Ok. After hours of searching I will try to sum up where I believe is the problem.
1st) I have a NUC and I have static IP through my router. I guess I should have it through the NUC. I don’t know how to do that since there is no “import from USB” in the system tab. Probably the instructions are only applied to RPI.
2nd) I might have damaged the DNS and that’s why I can’t install any add-on. Again I don’t know how to change it. Maybe it is linked with the 1st issue.
3rd) I don’t know how and where to run the command “hassio su repair” (or something like that which I don’t remember exactly now), which could probably repair the DNS issue.
I was able to solve my problem. In the AdGuard Settings for Encryption you can check the option to redirect to HTTPS automatically. Don’t do it. After I checked this I was no longer able to enter the settings page. So I had to uninstall and reinstall. After enabling the encyption without checking the automatic redirect everything is working.
@frenck This add-on is great! Thanks for this. I did have one feature request which I added to github repo about being able to use the DoH options for outside the network connections but its not a huge deal. Was really easy to get set up for my local network and have all DNS go through it.
One thing I couldn’t figure out though, is there a guide or something for setting it so that Home Assistant uses the add-on directly for all DNS queries? By default my router tells all devices on my network to send DNS queries to it which I then redirect back to the AdGuard add-on. And while this works I’d like to shortcut it and simply have my Home Assistant instance send all DNS queries directly to the add-on.
Are there instructions for doing this? I set my Pi device to use the add-on for DNS and I tried using the CLI and changing it with ha dns options --servers 127.0.0.1. I see that dns server in the list now but it still seems to be sending everything through my router. Is there a different way to do this?
Ah, I figured it out. I was looking at the details for the wireguard add on and it mentioned how to set up the DNS configuration if you use the adguard add on too, same 172 value worked here too. Still getting used to docker, forgot you have to use the IPs it gives out in these situations not the ones I’m used to.
can anyone provide more info/details about what i need to do to get this set up…
Ensure your Home Assistant device has a static IP and static external DNS servers! This is important! You WILL end up having issues if you skip this step. Also, please note, setting a fixed IP in your router is NOT static.
i dont really know how to do this, and all the link provided says is this:
I don’t want to be a bad or rude person or something, but if you don’t know what to do with that requirement, than you probably should not use this add-on.
Since using the AdGuard Addon it’s not possible to access local dns addresses like fritz.box i.e., in Pihole there was a so called Option „Conditional Forwarding“ Is this also available within AdGuard?
In case anyone comes across this, the answer is blindingly simple. Under the DNS settings, when specifying the upstream DNS, if you specify one as https AdGuard then does all requests over that DoH resolver.
The lower ‘bootstrap’ setting is the DNS server used by AdGuard to find the IP of the specified upstream DNS resolver.
If you want to see this for yourself, install tshark and run this command while restarting the add-on and other than some internal docker queries, you will just see entries relating to the DoH resolver domain. For any other machine you will see incoming queries but no outgoing one on port 53.
sudo tshark -i any -f "src port 53" -n -T fields -e frame.time -e ip.src -e ip.dst -e dns.qry.name
Release v2.3.2
Changes
Upgrades nginx to 1.16.1-r6
Update add-on documentation to use new YAML configuration format
