DNS Host not working since v0.98 of HA

[richard-scott]

I'm using Home Assistant v0.98.1 and since the 0.98 release I have been unable to use a hostname to find my VirginMedia Tivo.

My config is very simple:

- platform: virgintivo
  scan_interval: 3
  tvchannellists:
    enable: true
  tivos:
    1:
      name: Virgin V6
      force_hd: true
      #host: TIVO-C68000022751B8C
      host: 192.168.0.60

I have tried both TIVO-C68000022751B8C and TIVO-C68000022751B8C.home.lan for the hostname and neither work. An nslookup on that hostname works fine:

root@home-assistant:~# nslookup TIVO-C68000022751B8C
Server:         127.0.0.53
Address:        127.0.0.53#53

Non-authoritative answer:
Name:   TIVO-C68000022751B8C.home.lan
Address: 192.168.0.60

[bertbert72]

I'm running 0.98.1 too and don't have any problems resolving the hostname. This isn't likely as a result of a Home Assistant upgrade, since this functionality is using the Python socket library rather than anything provided by the HA framework.

I'm a bit stumped as to how this would stop working or why you can resolve at the command-line but not in the app. Are you running HA directly or is it within a container such as Docker?

[richard-scott]

Looks to be related to the recent HA DNS changes: https://community.home-assistant.io/t/name-resolution-problem-since-0-97-2/132201/71

It works if I use the FQDN now.

[bertbert72]

Ah ok. So it's a change in Hass.io that's caused the problem rather than the core Home Assistant stuff. At least you got to the bottom of it.