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
Raspberry Pi 3, 4+
What YunoHost version are you running
version: 12.0.16
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 ?
no
Describe your issue
Hi,
I’m hitting a persistent DynDNS SERVFAIL that doesn’t resolve on its own. It has now lasted over 18 hours.
The outgoing UPDATE is accepted (NOERROR), but the authoritative server returns SERVFAIL on the zone write to nohost.me. IN SOA, and the record never appears in the zone (confirmed via @ns0.yunohost.org returning empty). This points to the zone write / Dynette backend, not client-side signing or connectivity. My resolver reaches dyndns.yunohost.org and ns0.yunohost.org (80.67.164.13) fine.
Context: A few months ago, a fresh YunoHost install with a .nohost.me domain worked perfectly. Over the last two days I did three clean reinstalls and tried three different domains (od1n.nohost.me, gm-odin.nohost.me) and even a .noho.st one — all fail identically with the same SERVFAIL. Since changing the domain, the TLD, and reinstalling all give the same result, the cause seems to be server-side, likely related to the ongoing Dynette migration.
What happens:
sudo yunohost dyndns update -d gm-odin.nohost.me -f returns:
rcode SERVFAIL
;ZONE
nohost.me. IN SOA
The debug log shows the outgoing query is accepted (rcode NOERROR) but the final write to the zone fails with SERVFAIL.
The record never enters the zone. Querying your authoritative NS directly returns nothing:
dig +short gm-odin.nohost.me @ns0.yunohost.org
→ (empty)
The domain still resolves to 127.0.0.1 (its parked state), so no IP update has ever succeeded.
My side checks out:
Resolver works: dig dyndns.yunohost.org and dig ns0.yunohost.org both return 80.67.164.13
No pihole/custom configs in /etc/dnsmasq.d/, resolv.conf is clean
TSIG key is present in /etc/yunohost/dyndns/, subscription succeeded (I have the recovery password)
The update request is correctly signed and accepted — it’s the zone write that fails
Setup:
YunoHost version: [12.0.16]
Hardware: Raspberry Pi
Public IPv4: 93.142.214.187 (dynamic ADSL, no CGNAT — ports 80/443 reachable)
No IPv6
Could you please check whether my domain gm-odin.nohost.me is stuck in the Dynette migration, and if so, manually push it into the zone? Happy to provide any logs. Thanks.
Share relevant logs or error messages
sudo ls -la /etc/yunohost/dyndns/
total 12
drw------- 2 root root 4096 Nov 4 18:29 .
drwxr-xr-x+ 8 root root 4096 Nov 4 18:41 ..
-rw------- 1 root root 123 Nov 4 18:29 Kgm-odin.nohost.me.+165+1234.key
dig +short dyndns.yunohost.org
80.67.164.13
hideo@gm-odin:~ $ dig +short ns0.yunohost.org
80.67.164.13
sudo yunohost dyndns update -d gm-odin.nohost.me -f --debug 2>&1 | tail -40
783 DEBUG Reusing IPv6 from cache: None
815 DEBUG initializing root ldap interface
1115 DEBUG Formating result in ‘export’ mode
1127 DEBUG Now pushing new conf to DynDNS host…
1127 DEBUG id 6632
opcode UPDATE
rcode NOERROR
flags
;ZONE
nohost.me. IN SOA
;PREREQ
;UPDATE
gm-odin.nohost.me. ANY ANY
gm-odin.nohost.me. ANY ANY
gm-odin.nohost.me. ANY ANY
mail._domainkey.gm-odin.nohost.me. ANY ANY
_dmarc.gm-odin.nohost.me. ANY ANY
*.gm-odin.nohost.me. ANY ANY
gm-odin.nohost.me. ANY ANY
gm-odin.nohost.me. 3600 IN A 93.142.77.240
gm-odin.nohost.me. 3600 IN MX 10 gm-odin
gm-odin.nohost.me. 3600 IN TXT “v=spf1 a mx -all”
mail._domainkey.gm-odin.nohost.me. 3600 IN TXT “v=DKIM1; h=sha256; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC9bVJKssUCnMlYPB8xJ4sc0w0zkSeNKZyJxXFqk4aAg66snBWh90AYE4vtvkjIdCGbkpl69jYYDnQTNWNpw41P2EphQHlGgoA2HtjVu8OaXi+rNf7QMgCZZtUjmS8+eYRVXY2PAwwWeTGeZIIsXHVDUBbFqmUx1whXBYzwdge7FQIDAQAB”
_dmarc.gm-odin.nohost.me. 3600 IN TXT “v=DMARC1; p=none”
*.gm-odin.nohost.me. 3600 IN A 93.142.77.240
gm-odin.nohost.me. 3600 IN CAA 0 issue “letsencrypt.org”
;ADDITIONAL
1155 ERROR id 6632
opcode UPDATE
rcode SERVFAIL
flags QR RA
;ZONE
nohost.me. IN SOA
;PREREQ
;UPDATE
;ADDITIONAL
1156 INFO The operation ‘Update the IP associated with your YunoHost subdomain ‘gm-odin.nohost.me’’ could not be completed. Please share the full log of this operation using the command ‘yunohost log share 20261105-114306-dyndns_update-gm-odin.nohost.me’ to get help
1160 DEBUG action executed in 0.751s
1160 DEBUG lock has been released
1160 ERROR Could not update IP address to DynDNS
hideo@gm-odin:~ $ dig +short gm-odin.nohost.me @ns0.yunohost.org
hideo@gm-odin:~ $ dig +short gm-odin.nohost.me @8.8.8.8
hideo@gm-odin:~ $ dig +short gm-odin.nohost.me
127.0.0.1
sudo yunohost --version
yunohost:
repo: stable
version: 12.0.16
yunohost-admin:
repo: stable
version: 12.0.7.1
yunohost-portal:
repo: stable
version: 12.0.10
moulinette:
repo: stable
version: 12.0.4
ssowat:
repo: stable
version: 12.0.3