My noho.st domain won't update dyndns

I have searched the forum for similar issues

on

This category is for general issues(=something is broken) regarding YunoHost, NOT apps.

on

This form is written in English but feel free to write in French if you’re more comfortable!

on

What type of hardware are you using

Other ARM board

What YunoHost version are you running

12.1.40.1

How are you able to access your server

The webadmin

Are you in a special context or did you perform specific tweaking on your YunoHost instance ?

a little

Describe your issue

i am currently unable to update my ynh dyndns noho.st domain, as of today.

i tried sudo yunohost dyndns update --force on the server. after doing so, the diagnosis still shows the old IP and i can’t access my server via the web. yunohost.local works, and custom domains (non noho.st) work.

Share relevant logs or error messages

i don’t have any error messages, update force returns with a success message.

I can confirm this. I checked ns0, ns1 and “ns2 .yunohost .org” with dig and my own domain + subdomains. ns1 is out of sync and repopulates public DNS with old IPs. This happens with ipv4 and ipv6.

i had some moments where it was working again yesterday, but then today it is again broken.

do you know if it is possible to avoid using ns1?

I don’t think you can. We just have to hope that an admin sees this and fixes it on their side.

@YunoHost

Hello,
I change something on the infra to fix that, I guess it’s solved could you confirm ?

Nobody gives a domain that i can test… (and setup a test env for that take time :confused: )

Have a nice day (or night),

on my domain it is currently working, but i don’t know how to test the different ns things, so best to wait for a more savvy user to chime in. as mentioned, it would sometimes resolve, but mostly not.

surely you have a test domain always set up for noho.st or similar? otherwise we are your dyndns guinea pigs! and it’s very frustrating when it breaks because we can’t get around it on our own.

my domain is boot.noho.st.

i checked in terminal with a little loop. you basically check “against” the nameserver ns0 - ns2.

for ns in $(dig +short NS nohost.me); do echo “$ns”; dig @“$ns” whatever.nohost.me A +noall +answer; dig @“$ns” whatever.nohost.me AAAA +noall +answer; done

this basically does: for every NS (NameServer) it finds, it prints the address, checks name resolution of ipv4 (A) and ipv6 (AAAA), the end

Looks like everything is in sync again, thanks :+1:

We have some functionnal tests on dyndns domain add and recovery operations indeed. But it’s when we push a commit on yunohost repo.

I don’t think we have that on a regular monitoring :confused: