Quantcast
Viewing all articles
Browse latest Browse all 104808

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

@SpikeyGG wrote:

I searched through the forum and found this post which sounds very similar to mine but it seems to be specific to the philips hue.

I am re-configuring my network trying to be as “IP-less” as possible – using my local DNS (pihole) servers to resolve all the devices in and around the house and writing rules on my router which are abstracted to use the local DNS names instead of hardcoded IPs. I’d like to do the same thing with Hassio but I’ve realized quickly that nearly all the components configuration.yaml entries require hardcoded IP addresses if you’re not going to use discovery (which I cannot because VLANs).

Recorder - When using DNS in the engine string it fails
“(MySQLdb._exceptions.OperationalError) (2005, “Unknown MySQL server host ‘logger-box’ (-3)”)
(Background on this error at: http://sqlalche.me/e/e3q8)”

Sonos - when I supply the hostnames, I get these warnings and no devices are found. When I use the IP addresses of the devices it works. The autodiscovery doesn’t work, even when I specify the interface_addr option with the hostname of the IP on hass.io that I want it to use. Everything must be IP addresses for it to work on my setup.
Image may be NSFW.
Clik here to view.
image

Chromecast - I’m unable to get the autodiscovery to find my device and I cannot supply a hostname, only a host’s IP address.
Image may be NSFW.
Clik here to view.
image

AsusWrt - using a hostname causes an “invalid config” error.
Image may be NSFW.
Clik here to view.
image

Pi-hole - config docs say it will default to pi.hole but that doesn’t work for me, nor can I force it to the pihole name that I actually use.
Image may be NSFW.
Clik here to view.
image

ZoneMinder - using a hostname here causes an “invalid config” error.
Image may be NSFW.
Clik here to view.
image

Envoy - It states that you can leave the ip_address option off and it’ll default to the envoy hostname which appers to be true but it still cannot find my envoy device (even though I can ping it from my hassio device’s ssh).

I’ve tried names in all the configuration “host” fields and they fail. I’m running hassio on a raspberry pi so it’s dockerized and I wonder if this is the problem. I can ssh into the device and resolve all my local hostnames to IPs (using ping and nslookup) so it seems like it should work but everything gives me errors when I try to use the names instead of IPs.

Thoughts?

Posts: 5

Participants: 4

Read full topic


Viewing all articles
Browse latest Browse all 104808

Trending Articles