Jump to content

Specific Docker Container DNS Not Working


Recommended Posts

Posted

My homeassistant docker container stopped worked entirely a few days ago and I can't figure out why. The container needs to contact `cloud.nabucasa.com` to register a cloud connection for their subscription service. Although, for some odd reason, the DNS resolution fails for that specific website in this specific docker container (strange). I've tried reinstalled the docker container twice, downgraded homeassistant version, and even tried a non officially maintained docker repo by the linuxserver guys. Nothing helps

 

Output from NginxProxyMananger (this container works):

10.0.0.3:8888/dockerterminal/NginxProxyManager/

/tmp # ping cloud.nabucasa.com

PING cloud.nabucasa.com (3.210.155.223): 56 data bytes

--- cloud.nabucasa.com ping statistics ---

26 packets transmitted, 0 packets received, 100% packet loss

/tmp # cat /etc/resolv.conf

nameserver 8.8.8.8

/tmp # ping youtube.com

PING youtube.com (172.217.13.142): 56 data bytes

64 bytes from 172.217.13.142: seq=0 ttl=117 time=23.993 ms

64 bytes from 172.217.13.142: seq=1 ttl=117 time=20.992 ms

64 bytes from 172.217.13.142: seq=2 ttl=117 time=19.273 ms

--- youtube.com ping statistics ---

3 packets transmitted, 3 packets received, 0% packet loss

round-trip min/avg/max = 19.273/21.419/23.993 ms

/tmp #

 

Output from homeassistant (this container fails):

10.0.0.3:8888/dockerterminal/homeassistant/

root@NAS:/# ping cloud.nabucasa.com

ping: cloud.nabucasa.com: Try again

root@NAS:/# cat /etc/resolv.conf

nameserver 8.8.8.8

root@NAS:/# ping youtube.com

PING youtube.com (172.217.13.142) 56(84) bytes of data.

64 bytes from yul02s05-in-f14.1e100.net (172.217.13.142): icmp_seq=1 ttl=118 time=22.7 ms

64 bytes from yul02s05-in-f14.1e100.net (172.217.13.142): icmp_seq=2 ttl=118 time=23.9 ms

64 bytes from yul02s05-in-f14.1e100.net (172.217.13.142): icmp_seq=3 ttl=118 time=19.3 ms

64 bytes from yul02s05-in-f14.1e100.net (172.217.13.142): icmp_seq=4 ttl=118 time=19.1 ms

64 bytes from yul02s05-in-f14.1e100.net (172.217.13.142): icmp_seq=5 ttl=118 time=14.6 ms

64 bytes from yul02s05-in-f14.1e100.net (172.217.13.142): icmp_seq=6 ttl=118 time=20.1 ms

--- youtube.com ping statistics ---

6 packets transmitted, 6 received, 0% packet loss, time 5007ms

rtt min/avg/max/mdev = 14.607/19.955/23.889/2.966 ms

root@NAS:/#

 

As you can see, both have internet access, both are using 8.8.8.8 dns, both can resolve youtube.com but only one can resolve cloud.nabucasa.com. The unraid host has no problem resolving cloud.nabucasa.com, its ONLY some of my dockers which fail, I'm stumped.

 

I've tried setting homeassistant up with host network mode (as recommended), also tried giving it it's own dedicated IP and tried it in bridge mode. All modes result in the same behavior.

 

Please offer any guidance, thank you!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...