Closed davidrhunt closed 5 years ago
My guess is this is a duplicate of https://github.com/home-assistant/hassio/issues/663 ... if it is please try out the workaround at the bottom of the thread and close this issue.
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:
Is this still an issue you are experiencing? Can you please try upgrading to the latest version of Home Assistant (0.90) and report back if this is still a problem? Thanks!
Not close on the the specs, but I had the same issue of not being able to get to any external sites. Could ping by IP but not name - 0.89.x through 0.90.1). My setup is a PI3 running ubuntu mate with home assistant in docker (running 0.90.1). Once i created /etc/docker/daemon.json in Ubuntu and added my local router as the dns and rebooted everything worked. Followed this link: https://l-lin.github.io/post/2018-09-03-docker_ubuntu_18_dns/
Hope this helps someone.
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 👍 This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Home Assistant release with the issue:
Home Assistant 0.80.1
Last working Home Assistant release (if known): This hasn't worked since I started using hassio, only recently debugged and understood the issue. I tried updating the OS from the previous Resin OS to the news Hass OS. I tried turning off the Pi Hole add-on. I tried disabling DuckDNS and Lets Encrypt. None of these experiments changed the behavior. The only fix was changing the DNS configuration as outlined below.
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io on Raspberry Pi running Hass OS
Component/platform:
iOS component, IFTTT component, any component trying to reach a host that requires DNS resolution
Description of problem: When trying to resolve DNS entries components get errors such as the traceback below.
The default
/etc/resolv.conf
on thehomeassistant
docker container is:With this setup the iOS component and IFTTT are unable to resolve DNS entries and the notifications do not work.
If I update
/etc/resolv.conf
on thehomeassistant
docker container to:Note:
10.0.1.240
is the IP on the Raspberry Pi running HassIO with the Pi-Hole add-on.then iOS notifications work as expected (haven't had a chance to test IFTTT yet).
Traceback (if applicable):
Additional information: Additional system information:
Hass OS
Home Assistant
Supervisor
If any further information is needed please let me know. Thanks!