hassio-addons / addon-adguard-home

AdGuard Home - Home Assistant Community Add-ons
https://addons.community
MIT License
374 stars 47 forks source link

Cannot get upstream DNS servers to work for the last month and a half now #505

Closed ZainAjam closed 2 months ago

ZainAjam commented 3 months ago

Problem/Motivation

I've been using adguard add-on for home assistant for a while now, and then in Feb it stopped working and certain Android TV apps that used adguard as its DNS server stopped working because they were not reaching the DNS server I allocated to the specific domain queries from the Android TV device. Since then, there have been 2 adguard add-on updates, but even with the updates, it has been a hit and miss. Would work sometimes and for some domains and not for others. I have no idea what is happening. It may even be due to syntax changes recently in the way that upstream DNS servers should be scripted, but I tried a number of different ways based on the support docs and I cannot figure it out.

Expected behavior

Forwarding of domain queries to my specified server for all domains specified

Actual behavior

Most domain queries do not get forwarded to the specified upstream DNS server

Temporary Workaround

I ended up pointing to dnsmasq add-on as the upstream DNS server for ALL domain queries, and then using dnsmasq's forwarding system to map specific domain queries to the DNS server addresses of my choice. This way I get the best of both the ad blocking from adguard and the DNS forwarding from dnsmasq. I just wish that I could go back to using adguard for both adblocking and DNS forwarding as I have been doing for years now.

How I have the upstream DNS server settings configured

1.1.1.1 1.0.0.1 8.8.8.8 8.8.4.4 [/peacocktv.com/]102.135.163.26 [/peacocktv.com/]129.232.164.26 [/disco-api.com/]102.135.163.26 [/disco-api.com/]129.232.164.26

I've also tried ...

1.1.1.1 1.0.0.1 8.8.8.8 8.8.4.4 [/peacocktv.com/]102.135.163.26 129.232.164.26 [/disco-api.com/]102.135.163.26 129.232.164.26

github-actions[bot] commented 2 months ago

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!