Core: Hassio does not resolve *.local domain names

[dovydasgulbinas]

Make sure you are running the latest version of Home Assistant before reporting an issue.

Home Assistant release (hass --version):

Hostname | hassio
-- | --
Type | resinos
OS | GNU/Linux
Host Control version | 1.0
Latest available version | 1.0

Version | 0.52
-- | --
Beta channel | false
Latest available version | 0.52

Current version | 0.50.2
-- | --
Latest version | 0.50.2

Component/platform:

This affects the following components:

• Homebridge-Home Assistant add-on
• All other components that need to resolve *.local domains

Description of problem:

I migrated from AIO to Hassio installer, but I ran into issues regarding use of *.local domain names.

Expected:

No errors during *.local domain resolution

Traceback (if applicable):

core-ssh:~# ping omc.local
ping: bad address 'omc.local'

# Another try with nslookup

Query the nameserver for the IP address of the given HOST
optionally using a specified DNS server
core-ssh:~# nslookup omc.local 192.168.0.1
Server:    192.168.0.1
Address 1: 192.168.0.1 hermes-machine

nslookup: can't resolve 'omc.local': Name does not resolve
core-ssh:~# 

I also tried to resolve a domain name while being attached to a docker homeassistant/raspberrypi2-homeassistant container:

bash-4.3# cat /etc/resolv.conf 
# Generated by NetworkManager
search hermes
nameserver 192.168.0.1
nameserver 8.8.8.8
nameserver 8.8.4.4
# NOTE: the libc resolver may not support more than 3 nameservers.
# The nameservers listed below may not be recognized.
nameserver 91.233.176.2
bash-4.3# ping omc.local
ping: bad address 'omc.local'
bash-4.3# nslookup omc.local 192.168.0.1
Server:    192.168.0.1
Address 1: 192.168.0.1 hermes-machine

nslookup: can't resolve 'omc.local': Name does not resolve
bash-4.3# 

Additional info:

The host machine running ResinOS resolves .local domains just fine

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[dovydasgulbinas]

@balloobbot

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

I just tried out the *.local name resolution still not working

[dovydasgulbinas]

@balloobbot

Prerequisites

• abillity to attach to host machine running resinOS
• knowlege on how to get docker container IDs

Steps to reproduce

# 1. Resolving IP on resinOS using my routers DNS address

    nslookup omc.local 192.168.0.1 

>>>   

    Server:    192.168.0.1
    Address 1: 192.168.0.1 gateway

    Name:      omc.local
    Address 1: 192.168.0.103 omc

<<<
 Expected: IP to be resolved (192.168.0.103)
 OK ✅


# 2. attaching to a docker container resolving IPs

    docker exec -it e2fd9cacaa20 bash
    nslookup omc.local 192.168.0.1

>>>

   Server:    172.30.32.1
   Address 1: 172.30.32.1
   nslookup: can't resolve 'omc.local': Name does not resolve

<<<
  Expected: IP to be resolved (192.168.0.103)
  FAIL 🛑


# 3. lets resolve non *.local domain (while still attached to container as in step #2.)

    nslookup google.com 192.168.0.1

>>>

  Server:    192.168.0.1
  Address 1: 192.168.0.1 TOSHIBA-PC-L300

  Name:      google.com
  Address 1: 216.58.214.238 bud02s24-in-f238.1e100.net
  Address 2: 2a00:1450:400d:809::200e bud02s26-in-x0e.1e100.net

<<<
 Expected: IP to be resolved to one of google servers
 OK ✅

[timdonovanuk]

This is an issue with Hassbian too (possibly related?). It seems to ignore the nameserver set in /etc/resolv.conf. I have no idea what's going on here, because for me some .local addresses are resolved and some are not (all are resolvable on other machines).

[dovydasgulbinas]

@timdonovanuk
There is a definitely issue with docker container networking setup. Because
as shown in my examples step 1. I just does not resolve *.local domain
names. So I can conclude that there are issues with hassbian

On Wed, 20 Dec 2017 at 19:00 timdonovanuk [e-mail] wrote:

This is an issue with Hassbian too (possibly related?). It seems to ignore
the nameserver set in /etc/resolv.conf. I have no idea what's going on
here, because for me some .local addresses are resolved and some are not
(all are resolvable on other machines).

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/8914#issuecomment-353120884,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMm1vACGOvcawpvRzNywrjxbXk8bAYxSks5tCT0agaJpZM4Ozx5X
.

>

Sent proudly from my iPhone 📱

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[balloobbot]

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍