Oh please yes! Using tcpdump I was able to determine that HA is bypassing my selected DNS server (AdGuard) and instead resolving via 1.1.1.1! This is despite the ha dns into command showing nothing of this server.
I have similar issues. Local DNS resolution only works for a certain time after restarting the local DNS server. I should ask my separate Adguard RPI instance under .222 which in turn is configured to resolve .fritz.box with the local FritzBox (.1).
Config:
I’d be happy over a fix. I worked better “in the past”.
The “only works for a certain time” had me thinking I was going mad and that I had network issues (the Pi I was trying to resolve is in another subnet in a DMZ…), it would work then break itself - not helpful behaviour!
I’m in the same boat… on HassOS would you believe it.
Please chime in on the issue that I’ve created :
Despite that issue being closed I’m still having intermittent DNS issues.
Where did those “locals” come from?
My router (10.1.1.1) is set up to use 1.1.1.1 and 9.9.9.9.
you can add dns servers in HA.
ha dns options --servers dns://1.1.1.1 --servers dns://9.9.9.9
I found I started having problems with dns when I enabled secure dns in my router but this seemed to fix it
Yeah I already added the 1.1.1.1 server but it’s redundant. If my router is not working HA is not going to be able to reach it. So I only really need 10.1.1.1.
So how do I remove a server, or the “locals”?
Yeah but you’re effectively using the dns in your router which in my case was the problem.
Edgerouter X has a good rep. I’d rather use that than rely on anything in home assistant.
1 Like
Well so does my FritzBox lol…
Presumably it’s only HA with this issue?
The HA Supervisor DNS log is not showing any errors.
But I’m getting intermittent connection to ABB, ARPANSA (UV index) , and local connections like the InFluxDB addon.
Hmm… local is a worry.
I had an issue this week with sources.list on my Proxmox box timing out on FTP.au.debian.org that I had never had an issue with before yet it was actually up so I ended up just changing the mirror in sources.list and it updated normally. Honestly these stupid inexplicable errors just wear me out.
1 Like
My issues were solved with the last coredns update.
For completeness :
➜ /config ha dns info
host: 172.30.32.3
locals:
- dns://192.168.11.2
servers:
- dns://192.168.11.2
- dns://192.168.11.1
update_available: false
version: 2020.11.0
version_latest: 2020.11.0
note : The 2nd server line (192.168.11.1) is redundant, 192.168.11.1 has 192.168.11.2 as its dns server.
How do I remove Google DNS (8.8.8.8) from “locals”?
1 Like
i’m not certain, but it might be configured through the host os (HassOS) in the /etc/resolv.conf file ?
# cat /etc/resolv.conf
# Generated by NetworkManager
search local
nameserver 192.168.11.2
What does yours look like ?
Ah bugger. I won’t have access to the host for a while. I didn’t pre-share keys before I went away.
You can change it in the Supervisor UI page.
3 Likes
Don’t know. I have stuff that comes and goes from there.
Weirdly I seem to be seeing the same with the latest docker image. I’ve verified /etc/resolv.conf has the correct servers by exec’ing bash in the container and can even get the nslookup command to resolve succesfully but HA itself will not. What am I missing here? I’d really prefer to not have to load up a VM just for HA 
Because DNS is so broken in HAOS that it isn’t even funny anymore & Pascal Vizeli has given up on trying to fix it.
1 Like