Can't update DynDNS after upgrading server with reinstall

Support
, ,
1

What type of hardware are you using: Old laptop or computer
What YunoHost version are you running: 12.1.40.1
How are you able to access your server: The webadmin
SSH
Direct access via physical keyboard/screen
Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: I don’t believe my Yunohost is specifically tweaked

Describe your issue

I have an old server that’s been in storage because I couldn’t get it to work with my ISP for a year or two. I got it out after moving again, and the software was too old to upgrade to the newest version directly, so I set a recovery password for my domain (rockcloud.noho.st) and reinstalled.

After fussing with the router to get IPv6 working and set up port forwarding, now I’m getting an error where DynDNS fails to update my IP, complaining that the peer doesn’t know or like the key I used.

I’ve tried checking for duplicate keys and deleting and refreshing the keys in /etc/yunohost/dyndns, unsubscribing and resubscribing my domain, setting the server to use IPv4 only, and even creating a new domain from scratch and none of these have helped. Force updating via cli gives the same result.

Share relevant logs or error messages

args:
  domain: domain3.tld
  force: false
ended_at: 2026-08-21 18:13:34.487827
error: Could not update IP address to DynDNS
interface: api
operation: dyndns_update
parent: null
related_to:
- - domain
  - domain3.tld
- - domain
  - domain3.tld
started_at: 2026-08-21 18:13:32.851405
started_by: ******
success: false
yunohost_version: 12.1.40.1

============

2026-08-21 12:13:33,920: INFO - Update needed, going on...
2026-08-21 12:13:33,923: DEBUG - Reusing IPv4 from cache: xx.xx.xx.xx
2026-08-21 12:13:33,924: DEBUG - Reusing IPv6 from cache: xx:xx:xx:xx:xx:xx
2026-08-21 12:13:34,015: DEBUG - Formating result in 'export' mode
2026-08-21 12:13:34,068: DEBUG - Now pushing new conf to DynDNS host...
2026-08-21 12:13:34,069: DEBUG - id 18996
opcode UPDATE
rcode NOERROR
flags 
;ZONE
noho.st. IN SOA
;PREREQ
;UPDATE
domain3.tld. ANY ANY
domain3.tld. ANY ANY
domain3.tld. ANY ANY
domain3.tld. ANY ANY
mail._domainkey.domain3.tld. ANY ANY
_dmarc.domain3.tld. ANY ANY
*.domain3.tld. ANY ANY
*.domain3.tld. ANY ANY
domain3.tld. ANY ANY
domain3.tld. 3600 IN A xx.xx.xx.xx
domain3.tld. 3600 IN AAAA xx:xx:xx:xx:xx:xx
domain3.tld. 3600 IN MX 10 rockcloud
domain3.tld. 3600 IN TXT "v=spf1 a mx -all"
mail._domainkey.domain3.tld. 3600 IN TXT "v=DKIM1; h=sha256; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC5/dY4sPs3Y3QCIfz6jDUU2bzjXzUAGsLCodNY1Z7hP2ph4K5Y1xHxsj8wMF6y8+Uq4oc5Jkhj9meXkE2NxrzDNquOVbD9BNWWP3XVf7uLb15TXLOIIJymYv165KitjUS3o37QJA7QW/A4Zdawji3S3xNG0FRMSbOeqVs0dH4OgwIDAQAB"
_dmarc.domain3.tld. 3600 IN TXT "v=DMARC1; p=none"
*.domain3.tld. 3600 IN A xx.xx.xx.xx
*.domain3.tld. 3600 IN AAAA xx:xx:xx:xx:xx:xx
domain3.tld. 3600 IN CAA 0 issue "letsencrypt.org"
;ADDITIONAL
2026-08-21 12:13:34,486: ERROR - The peer didn't like the signature we sent
2

Hello, and welcome back. :slight_smile:

Sorry about that bug. I think I fixed the issue. Can you confirm so?

3

I don’t know what magic you just did, but it seems to have worked. Thank you so much!

I’ve noticed that quite a few people seem to be having similar issues on this forum over the past few days. For posterity’s sake, would you be willing to share if there’s anything else I/we could have done or could to avoid this issue in the first place or fix it in the future?

4

Yes, I am about to browse the recent reports and notify them of the resolution. :slight_smile:

There was a service in our infrastructure that passes the domain registration to the DNS that was down, and we were not notified of it. Fixing it and restarting it updated the DNS.