Sophos Firewall Dynamic DDNS failed to connect FreeDNS

Ok after I have tried many combinations, I finally cracked it.

Unfortunately, my success was only short-lived.

For some unknown reason, on the next day I checked success became failed 

Unfortunately, my success was only short-lived.

For some unknown reason, on the next day I checked success became failed 

The hostname: Just to be sure, could you review your freeDNS config, as this field is case sensitive? 

Believe me, I have gone thru it many times, in fact, I am sick of typing.
I typed all the details once, like hostname, update key on a text file,
so that I don't key in character by character, I just copy and paste.
Repeat the steps when it fails.

Please note that when I discovered it was unsuccessful this morning,
My DDNS connection Namecheap also failed, all the columns show the value,
except that:
Last updated IP  = blank
Last updated status = blank
Last updated time = blank
Failure reason = blank

Pressing the edit button and copy and paste the required details and save again, did not solve the problem.
I had to delete the whole entry, reboot the FW and start over again.

There is something not right. Personally I don't think it is stable or some bugs may be the culprit, base on my assumption. 

Hello,

Is your IP NATed, or do you see the Public IP in your Sophos Firewall?

Regards,

Actually I should be using = use IP port = pointing to my public WAN IP.
I made a mistake in the picture attached.
My firewall is connected to VLAN switch and it is connected to Fibre Broad Terminal Unit.
My firewall is NOT connected to a router. 
So to answer your question I am using  = use IP port, because my WAN IP is publicly reachable on the internet..

Please if someone out there is free, got some spare time, create a new domain, by registering a new account from freedns.afraid.org
Test it on DDNS service in SFOS. 
If it is working please share your settings.
If it is NOT working, "raise your hand up" and alert the Spohos Team, telling them something is not working in the firewall code.
Thank you.

I was running into an error as well. 

But it is caused by freedns. If the password is to long, it will not work. 

The online help is wrong here. We are not using the Update Key. 
We are using Accountname + password for FreeDNS. Will get the online help updated. 

Setting is straight forward: 
Hostname + Username + Password. 

Used an 16 digit password, which fails. Apparently, the API of FreeDNS does not support long passwords. With 8 digits, it worked. 

Thanks for taking time to look into the problem. I think this problem was not discovered for a long time, why? Because I read somewhere in the forum, someone had this same issue, a couple years back.

Sadly, it is probably no one has actually tested it out, rigorously, before it was released it to the public.  

Sorry, can be specific here, please. I know you got it working. I am so excited!!!

Account name = means UserID that is registered with freedns.afraid.org?

Password = means the login password into freedns.afraid.org, but just use the first 8 digits starting from the left?

Hi, 

Don't need to reply my questions posted to you.

Yes totally, correct!

hostname = type in the registered subdomain.domain.tld (e.g. xyz.chickenkiller.com) within freedns.afraid.org

Interface = I select the PortX (Port number that is assigned to WAN interface- showing the public IP address)

IPv4 address = I select Use port IP because my firewall WAN interface is not using private IP address.

Service provider = select FreeDNS - of course.

Login name = User ID of your account with freedns.afraid.org.

Password = password used for login into the freedns.afraid.org web portal. If the password is more than 8 digits long, just copy the first 8 digits and paste it in the blank box.

Thank you! 

By the way, the 8 digits was just my test case. Apparently, the API has a cap of 15. Which is one digit less than the max of the website (16). 

Feel free to reach out to FreeDNS. I just found an old statement from 2017 about this with Sophos UTM (same issue). 

I already did, sent an email  to the Josh, the PIC of FreeDNS, a few days back, but so far no reply.