DynDNS migration

Hey there!

You might have seen some DynDNS issues these last few days. If not, that’s good :smiley:

We are testing a new version of our “DynDNS registration software”, Dynette and are going to migrate the service to a Debian Trixie and YunoHost 13 machine.

So, if you use our DynDns service (and have a domain ending with .ynh.fr, .nohost.me or noho.st), please ping us (here or on the Support Matrix room) if you find any issues these next few days.

There should not be any issues with the actual DNS service as we have a backup DNS server that will handle domain requests while the migration is in progress.

I’ll try to be as fast as possible to reduce the downtime at most.

5 Likes

Alright, migration finished without any major issues ! :tada:

6 Likes

Great work, mate. Only minor issues here; looks like it went pretty smooth. All the effort you put into this platform is deeply appreciated.

1 Like

Ah, can you point to me which issues you have, if still present ?

Nothing too tragic, mate. Everything is all good now. On the 11th the system sent me this:

ERROR id 53652
opcode UPDATE
rcode SERVFAIL
flags QR
;ZONE
nohost.me. IN SOA
;PREREQ
;UPDATE
;ADDITIONAL
ERROR Could not update IP address to DynDNS

But haven’t had any issues since and nothing shows in Diagnosis.

1 Like

Ah yes, debug log filled the disk and broke named that day :smiley:

1 Like

connection timed out…

https://paste.yunohost.org/raw/epucopedik

Weird. I restarted named, can you retry ?

Oh. I opened a ticket related to DynDNS, which might be related to this one (?). Here is the topic: DynDNS update: ERROR The peer didn't like the signature we sent sorry if it is related and the discussion better belongs here, I had not found this thread in my initial search.