DuckDNS not updating IP - Hassio Add-on

Unsure what happened here - But it seems about 1-2 months ago DuckDNS stopped getting updated by my HassIO Addin.

I only know it was 1-2 months ago from the DuckDNS control panel.

It looks like the add-on is “working” but just not pulling the IP and updating - I dont have Let’s Encrypt running, @ I have an OpenVPN AS running on that IP already using 443, I just want the DDNS to be updated /shurg

For Reference - here are some screen shots from the DDNS UI. Also, for add ons, I have Samba, HomeBridge, and Pi-Hole running. The host rPI DNS is set to 8.8.8.8, 8.8.4.4

A little more sleuthing on my end.

I SSHed into the box using the SSH add-on, and if I run

nano /etc/resolv.conf

I get the following:

nameserver 127.0.0.11
options ndots:0

if i try nslookup or a ping to google they fail

core-ssh:~# nslookup google.ca
nslookup: can't resolve '(null)': Name does not resolve
core-ssh:~# ping google.ca
ping: bad address 'google.ca'

interestingly, my sensors like DarkSky are working.

I tweaked my resolv.conf to add google DNS

nameserver 127.0.0.11
nameserver 8.8.8.8
nameserver 8.8.4.4
options ndots:0

and now I can ping and resolve google.

Any thoughts on what this could be? I am 99.9999 percent sure I set the resin config to use google DNS, and hass “seems” to be getting DNS out using something for things like DarkSky, but not others like DDNS?

Also - after making these changes, I removed and reinstalled duckdns and still get the same entries in the log so now i’m really stumped

starting version 3.2.2
Thu Feb  8 11:23:18 AST 2018:

I’m having the exact issue in my setup. Ideas anyone?

I know it’s not the right approach, but I binned it and installed a duckdns docker in my unraid box - I’ll come back to this at some point after a few updates I figure.

Is that right? Shouldn’t it be 127.0.0.1 for localhost?

EDIT: Some googling seems to indicate a Docker-thing… Ah, ok.

1 Like