Hello, new user of Home Assistant here, and I’m excited to get back into home automation. I recently set up an Intel NUC with the thought of making it my home ‘server’. I originally wanted everything on Docker, and it worked great. I have PiHole on Docker, among a couple of other things.
But, I soon realized that I wouldn’t have access to add-ons within HA - I feel that I will want that. So, let’s run it in a VM using the HA OS instructions at Linux - Home Assistant. In general, it works fine. I can connect to the GUI. But, dns-masq in libvirtd by default runs a DNS server that conflicted with pihole and prevented pihole from starting. I found that I could edit the libvirt network definition with <dns enable='no'/>, and pihole on docker and HA on libvirt mostly coexist. The one problem I have is that DNS resolution for HA is lacking.
From the HA OS console, I can ping google.com, but not any other domain that I can think of. This first manifested itself when I tried to install an add-on and received “‘AddonManager.install’ blocked from execution, no host internet connection”. I can ping IP addresses directly.
I think that I need to find a way to reenable DNS for the default network in libvirt (it is the only network at the moment), but only make that available to that network so that it doesn’t block pihole from access to port 53 on the host. Any thoughts on how I can do that? I’ve looked at different networking in libvirt like bridge and direct, but so far I have not been successful.
Alternatively, (maybe ideally??) if I could set the DNS manually within the HA OS, and ignore the lack of DNS resolution in libvirtd, that would be great.