Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Resolving issues with DNS server on the same machine distributed over DHCP

See original GitHub issue

Home Assistant Core release with the issue: > 104.3

Home Assistant release with the issue: >= 198

Operating environment (HassOS/Generic): Home Assistant (Hassio) Docker Install on Raspbian

Supervisor logs:

20-02-07 08:24:50 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-02-07 08:24:55 WARNING (MainThread) [hassio.updater] Can't fetch versions from https://version.home-assistant.io/stable.json: Cannot connect to host version.home-assistant.io:443 ssl:None [Try again]`
20-02-07 08:16:07 ERROR (MainThread) [hassio.store.git] Can't update https://github.com/hassio-addons/repository repo: Cmd('git') failed due to: exit code(128)
  cmdline: git fetch --depth=1 --update-shallow -v origin
  stderr: 'fatal: unable to access 'https://github.com/hassio-addons/repository/': Could not resolve host: github.com'.

hassio_supervisor:

➜  ~ cat /etc/resolv.conf 
search local.hass.io
nameserver 172.30.32.3

hassio_dns:

bash-5.0# cat /etc/resolv.conf
search fritz.box
nameserver 127.0.0.11
options ndots:0

Description of problem:

Home Assistant (Hassio) can’t update the Home Assistant Core version, Home Assistant Addons
Hosts can’t be reached via DNS
I’ve AdGuard as a Home Assistant Addon installed and distributed over my router’s DHCP server. Everything else is working fine, Home Assistant Core itself and other devices in my network can use the AdGuards DNS server just fine

After removing the Raspberry’s IP from the router’s DHCP server (DNS server IP) and restarting the machine, it can resolve the urls again

Issue Analytics

State:
Created 4 years ago
Comments:9 (2 by maintainers)

Top GitHub Comments

1reaction

niklaswacommented, Feb 7, 2020

So apparently you have to set an external DNS server manually in that situation as stated here. I still don’t get why, because I wanted to use AdGuard on the Pi itself too, but ok. 😄

0reactions

pvizelicommented, Jun 16, 2021

We “fix” the issue with Eero. They response wrong to the AAAA query (maybe someone needs to tell that company how IPv6 works with IPv4, but in that case, they should not produce network equipment. Our internal DNS solution bypass eero in that case to provide a working system.