Hassio DNS issue after upgrading router esphome (devicename.local.local)

Hey there,

I have a strange DNS issue, that hopefully someone can help with, I first noticed this becuase I have ESP home installed and ESPhome was showing devices as being offline despite me being able to connect to them and the devices reporting back live data to HA.

I think this issue was cause by me switching Wifi routers at home from a TPlink router to a Vodafone home broadband one since installing HA. I should mention that the old router and new one have identical network settings both in terms of security and DHCP.

What I’ve noticed is that I can ping my EPShome devices over my network e.g. boiler.local is pingable from my laptop, but not if I SSH into hassio and ping from there. I ran

ha dns logs

and got some strange looking results:

[INFO] 172.30.32.1:48098 - 18938 "A IN boiler.local. udp 30 false 512" NXDOMAIN qr,rd,ra 105 0.023268828s [INFO] 172.30.32.1:48098 - 19962 "AAAA IN boiler.local. udp 30 false 512" NXDOMAIN qr,rd,ra 105 0.029413767s [INFO] 172.30.32.1:33861 - 42816 "A IN boiler.local.local.hass.io. udp 44 false 512" NOERROR - 0 0.000189849s [ERROR] plugin/errors: 2 boiler.local.local.hass.io. A: unreachable backend: no upstream host

Note the ‘local.local’ above.
So this explains why I can’t ping the device from hassio, and why esphome is reporting incorrect statuses and showing devices as offline despite them working, but I’m not sure how to solve this.

I can ping google.com fine.

Not sure where this local.local has come from or how to fix it!

Any ideas?

Thanks

1 Like