OPNsense Forum
Archive => 22.7 Legacy Series => Topic started by: aimdev on October 07, 2022, 09:36:35 am
-
I use dns on 853, forwarding port 53 to port 853, blocking other dns servers.
Recently I added Home Assistant, which appears to use 1.1.1.1:853 or 1.0.0.1:853.
There are issue's with Home Assistant and altering its dns, it feels ever so lonely and checks the mothership every 10 minutes or so.
Incidentally, with the log on the rule (used for check internet usage) it when goes beserk, tops up the log,
and the syslog monitor system ramps up with loads of backlogs.
Is there a way to force it to use unbound, as the clone of the port 53 forward didn't seem to work.
-
If it's using 853, it suggests is using DoT which is TLS traffic. So above tcp layer on http(s). Dunno home assistant myself (don't use it) but if it can be altered in its config?
-
Apparently yes, but when I tried it, it didn't work. HA is dockerized , so the fallback dns is a 172 private address.
HA is tied down somewhat, others have had issues.
Preferable to see if its possible with Opnsense.
Yes, it is TLS, no its not using https.
-
Of course, I miswrote. DoH is on the layer.
The rule should work as its ip:853 . DoH is another thing.
-
On reflection I have decided to dump HA, so the question is now irrelevant to my requirements.