Local DNS!

[Benji2020]

Hi

Why is it that I can find post after post with people trying to get local network name resolution working and failing? There are some very bright people here, and they can’t find a solution to it.

I have an integration that needs to connect to a server name, no matter what I do I cannot get it to connect reliably, it works for a random amount of time then stops. Removing and re-adding is very hit and miss. Lookups from the host work fine (it is a ready-rolled image hosted in Hyper-V), or any other network device.

It seems that there are some DNS IP addresses hard-coded somewhere - and cannot be removed - which just causes confusion. We should have proper control over this.

PLEASE for the sake of everyone’s sanity can we have something done about this?! DNS options/update does not work reliably.

Cheers
Ben

DNS not working on homeassistant under Hassio

Anyone have any idea what this image is? homeassistant/armhf-hassio-dns From what I can tell, homeassistant is now offloading DNS requests to this. Problem is, homeassistant now keeps failing at any DNS requests that are internal to my network, which is a huge problem… From homeassistant container: root@hassio:/home/brad# docker exec -it homeassistant bash bash-5.0# cat /etc/resolv.conf search local.hass.io nameserver 172.30.32.3 bash-5.0# nslookup camera-server.home nslookup: can't resolve…

Name resolution problem since 0.97.2

Hi, I’ve got a security camera configured in my Hass.io installation. It’s receiving the image from a Raspberry Pi with Motion running on it. It’s configured like this in HA: camera: - platform: mjpeg mjpeg_url: !secret wozi_webcam_url still_image_url: !secret wozi_webcam_url_static name: Wohnzimmer Cam username: !secret archpi_motion_user password: !secret archpi_motion_pass verify_ssl: false So far, this working fine and the camera Lovelace card in my HA installati…

Thousands of 'Bad' DNS requests per second after update

After updating to the latest version (0.97.2) my network intrusion prevention system went nuts catching over six thousand ‘Bad’ DNS requests per second (yes, per second) from Hassio. Each request comes from a different source port on UDP protocol 17 destined for either 1.1.1.1 (CloudFair) or 9.9.9.9 (Quad9) destination port 53 (DNS) 2019-08-20 15:53:00.045 1 2027758 1 3 192.168.10.217 48028 1.1.1.1 53 17 dns bad-unknown ET DNS Query for .cc TLD true 2019-08-20 15:53:00.042 1 2027758 1 3 192.16…

Hass.io cannot use local DNS names in place of IP addresses in configuration.yaml

I’ve been futzing around with the hassio dns options and I discovered that mine was configured like this: ~ $ hassio dns info host: 172.30.32.3 latest_version: "1" locals: - dns://192.168.0.8 - dns://1.1.1.1 servers: - dns://8.8.8.8 - dns://1.1.1.1 version: "1" ~ $ The 192.168.0.8 is my pihole server and it should be coming from the DHCP assignment but I wondered if for reason HassOS/hass.io was using hardcoded dns://8.8.8.8 and dns://1.1.1.1 for name resolution. I tried manually setting the v…

Hass.IO - Baked-In DNS Client?

this is still happening for me… I’m using AdGuard and noticed that things weren’t resolving locally correctly. I got onto the core_ssh terminal plugin and discovered that queries are definitely NOT going through my AdGuard server. I did a simple nslookup of poopy.com and the tcpdump from my router showed it going thru 1.1.1.1, and the query was absent on AdGuard. My ha dns info command only shows my AdGuard IP!

[jschwalbe (Justin S)]

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.

[nodomain]

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”.

[Benji2020]

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!

[Tommmii]

I’m in the same boat… on HassOS would you believe it.
Please chime in on the issue that I’ve created :

DNS server settings ignored for resolving lan hosts.

[tom_l]

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.

[DavidFW1960 (David)]

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

[tom_l]

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”?

[DavidFW1960 (David)]

Yeah but you’re effectively using the dns in your router which in my case was the problem.

[tom_l]

Edgerouter X has a good rep. I’d rather use that than rely on anything in home assistant.

[DavidFW1960 (David)]

Well so does my FritzBox lol…
Presumably it’s only HA with this issue?

[tom_l]

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.

[DavidFW1960 (David)]

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.

[Tommmii]

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.

[tom_l]

How do I remove Google DNS (8.8.8.8) from “locals”?

[Tommmii]

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 ?

[tom_l]

Ah bugger. I won’t have access to the host for a while. I didn’t pre-share keys before I went away.

[tom_l]

You can change it in the Supervisor UI page.

[DavidFW1960 (David)]

@tom_l

How do I remove Google DNS (8.8.8.8) from “locals”?

Don’t know. I have stuff that comes and goes from there.

[andybaran]

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