Hi,
Strato DynDNS doesn’t work for me. I’m getting bad authentication:
08:10:01 ddns[22356]: Dynamic DNS update for xyz.de (Strato AG) failed:
08:10:01 ddns[22356]: DDNSUpdateError: The update could not be performed
08:10:01 ddns[22356]: Server response: badauth 123.456.789.123
08:15:00 ddns[22547]: An update has not been performed because earlier updates failed for xyz.de
08:15:00 ddns[22547]: Last failure message:
08:15:00 ddns[22547]: DDNSUpdateError: The update could not be performed
08:15:00 ddns[22547]: Further updates will be withheld until 2025-10-27 19:10:01.657350
Anyone using Strato DynDNS? I’ve created a password for DynDNS and I use the account number as user name for authentication.
Cheers
From the IPFire DDNS documentation on the providers it shows
It doesn’t mention the account number for the username. Are you sure that the username is not separately defined.
Maybe ask the Strato people what should be used for the Username.
I use this for login so I thought it will be the user name for DynDNS as well. I use a subdomain for DnyDNS, but this should be a problem. If I activate DynDNS for a domain or subdomain, I have to define a password for it, but not a seperate username. The password starts and ends with letters like “!” and “?”. Maybe this is a problem for IPFire?
I don’t believe so, although my password does not have those specific characters, however I do have characters such as ` % } ^ as well as characters and digits and it works fine with the IPFire updating.
Maybe try changing the password to only have characters and digits and see if that the works.
The url used to carry out the update is
https://dyndns.strato.com/nic/update
If you access this then you get a login box
Try your Username and Password out in there and see if it allows you to logon. If not then either the Username or the Password is incorrect.
I just tried some random entries and I got
badauth <my public IP>
which is the strato server giving me the same response as you got but with a different IP and done without any of the IPFire DDNS code.
I think that you need to get that Strato update login to work first.
Found this page on the Strato site
https://www.strato-hosting.co.uk/faq/hosting/this-is-how-easy-it-is-to-set-up-dyndns-for-your-domains/
This suggests that the username is the domain name that your host name is attached to. See section 2 on that link page.
So it gives an example of the Hostname being mypc.desiredname.de and the username being desiredname.de
If I use the domain name, I get the message notfqdn <my public IP>
Maybe try then with the fqdn as it seems to not be happy with the username being only the domain name.
Nice translation for password 
Actually the domain name is a fqdn, as in the example.
At least the badauth is gone, now it’s something different. I guess it’s because the part for the host name is missing when accessing the update website via browser.
You need to figure out what entry from your account you need to use for the User.
According to that Strato page they are using the DynDNS v2 protocol from dyndns.org which is what is used in the IPFire DDNS code.
I would suggest contacting Strato and ask them what you should consider as the Username for your account for the DDNS Updating.
Atm it’s blocked because of too many failed attempts, but if it continues not working with the fixed log on credentials and the new error message, I will contact them. Thanks for your help.
Maybe this means that the username and password worked but then it did not get the host name afterwards.
If that is the case then you should go back into the IPFire DDNS page and change the Username to the one you used above. Then press the Instant Update button and see if it updates now.
I think so as well, atm I get again:
23:20:00 ddns[6877]: An update has not been performed because earlier updates failed for xyz.de
23:20:00 ddns[6877]: Last failure message:
23:20:00 ddns[6877]: DDNSUpdateError: The update could not be performed
23:20:00 ddns[6877]: Further updates will be withheld until 2025-10-28 07:15:02.161859
I changed the log on credentials in ipfire and need to wait now until it’s unlocked again.
Yes, waiting is the best thing now. Later on tomorrow morning hopefully you will have good news. 
Tried again, getting badauth in ipfire again, while it’s working with the notfqdn message via webbrowser.
Only things I can think of then are to discuss with Strato and/or test out a dynamic DNS updater package on a PC on your network.
For Linux there are several packages but the one that has been around for a long time is ddclient.
If your systems on the network are windows based then there are also updater packages for windows but I have no idea about any names, although Strato mention two ion their FAQ page for updating.
Strato confirmed the log on credentials and blaims the implementation to be wrong.
Strato was added to the DDNS list in 2014. Then in 2015 the entry was updated with the following commit.
strato: Add mx and backupmx flags to update request.
Add the deprecated mx and backupmx flags to the update request for strato,
because this provider still uses them. The providers implementation anyway seems
to be broken because already set entries get lost when an update is performed
without given mx and backupmx flags.
Fixes #10754.
Those deprecated mx and backupmx flags that are provided only for the Strato provider are still present in the code.
Looking through their website it looks to me that the only way you can get a free DDNS service with Strato is by having Hosting package with them.
I am not sure if that has always been the case but with that situation I am unable to test the situation out and do any problem solving directly.
It might be that Strato changed their update process since 2014/2015.
Maybe another Forum user is using Strato for DDNS and can confirm if they have it working or not?
According to the German Strato DDNS FAQ
https://www.strato.de/faq/hosting/so-einfach-richten-sie-dyndns-fuer-ihre-domains-ein/
it says
Mit diesen Beispielangaben könnte ein manuelles Update der DynDNS Domain wie folgt aussehen:
https://ihredomain.de:DynDNS-Passwort@dyndns.strato.com/nic/update?hostname=subdomain.ihredomain.de&myip=192.XXX.X.X,2003:8106:1234:5678:abcd:ef01:2345:6789
So with that you could try the manual update via the browser and confirm that you get back a good <yourip> message. This should be the message response based on the input in the IPFire bug (#10754) that the 2015 update mentioned above was related to.
The &myip= line is in IPv4,IPv6 format. I believe that you can just use your IPv4 IP.
This process is different with what you tried on the browser yesterday so the above might be worth trying to confirm if you can get the update done successfully manually. If that occurs then it would indicate some change needed in the Strato entry in the IPFire Providers code.
2 Likes
Thank you. I’ve tested the URL and I get
nochg <MY-IP>
So I checked the log and the last entry is
11:45:01 ddns[9518]: Dynamic DNS update for xyz.de (Strato AG) successful
I didn’t change anything and now it looks like it’s working… 
