GoDaddy DDNS error

ascabral

After a power outage, my Godaddy DDNS do not update anymore. I tryed to create a new configuration with a new set of API keys, but the error continues:

Sep 10 20:30:22	php-cgi	57256	rc.dyndns.update: Dynamic Dns (redacted): Current WAN IP could not be determined, skipping update process.
Sep 10 20:30:22	php-cgi	57256	rc.dyndns.update: Dynamic DNS godaddy (redacted): Public IP address could not be extracted from Check IP Servic

Sep 10 21:10:17	php-cgi	67790	rc.dyndns.update: phpDynDNS (vpn): (Error) Authenticated user is not allowed access.

Now I am using other DDNS service (No-IP), and it is working normally.

Gertjan

@ascabral said in GoDaddy DDNS error:

Public IP address could not be extracted from Check IP Servic

Strange.

Go here :

You see the URL ?
Click on it :
http://checkip.dyndns.org
You should see your WAN IPv4.

pfSense uses the same URL to obtain the same info.
Or, it didn't work out.

[24.03-RELEASE][root@pfSense.bhf.tld]/root: curl http://checkip.dyndns.org
<html><head><title>Current IP Check</title></head><body>Current IP Address: 82.135.26.241</body></html>

bmeeks

GoDaddy changed the terms of their free dynamic DNS service back in late spring this year without much notification. Here is a Reddit thread discussion of this change: https://www.reddit.com/r/selfhosted/comments/1cnipp3/warning_godaddy_silently_cut_access_to_their_dns/. They removed access to their dynamic DNS API unless you have at least 10 domains hosted with them.

I was bitten by this change. Got zero notice of any upcoming changes from GoDaddy (or at least nothing appeared in my email). I swapped my dynamic DNS account over to a free Cloudfare one.

Gertjan

@bmeeks
Thanks for the reminder ... I knew there was a issue somewhere.
This explains the :

@ascabral said in GoDaddy DDNS error:

(Error) Authenticated user is not allowed access.

as the service was ditched a couple of months ago.

But this has nothing to do with the "DDNS supplier" :

@ascabral said in GoDaddy DDNS error:

Public IP address could not be extracted from Check IP Service

as this is a test been done locally by pfSense and can only fail, imho, if local DNS has been messed up.

bmeeks

@Gertjan said in GoDaddy DDNS error:

@bmeeks
Thanks for the reminder ... I knew there was a issue somewhere.
This explains the :

@ascabral said in GoDaddy DDNS error:

(Error) Authenticated user is not allowed access.

as the service was ditched a couple of months ago.

But this has nothing to do with the "DDNS supplier" :

@ascabral said in GoDaddy DDNS error:

Public IP address could not be extracted from Check IP Service

as this is a test been done locally by pfSense and can only fail, imho, if local DNS has been messed up.

I have seen the "could not be extracted" error in my own setup from time to time. It seems to happen during a restart of the interface (as in when my ISP has a short outage for some reason). I suspect, but without any proof or deep knowledge, that the DDNS client might be trying to grab the WAN external IP before the interface restart is fully complete.