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
Old laptop or computer
What YunoHost version are you running
Version not at hand; I can provide it if needed.
How are you able to access your server
SSH
Are you in a special context or did you perform specific tweaking on your YunoHost instance ?
Home server behind a router and NAT. Home Assistant is exposed through an affected nohost subdomain.
Describe your issue
Home Assistant is reachable locally, but the affected nohost subdomain becomes intermittently unreachable from external networks. The failure affects different devices, including a phone.
The public DNS zone is inconsistent between authoritative YunoHost name servers:
ns0-yunohost-org (80.67.164.13) returns 83.6.200.46
ns1-yunohost-org (91.224.148.93) returns 83.6.201.191
The two authoritative servers also report different SOA serials:
ns0: 2026152076
ns1: 2026150504
The correct address is 83.6.200.46. It presents a valid Let’s Encrypt certificate for the affected Home Assistant subdomain and returns HTTP 200 through nginx and Home Assistant. The other address, 83.6.201.191, accepts TCP port 443 but hangs during TLS, so clients resolving it time out.
I forced an update on the server with: sudo yunohost dyndns update --force --debug
It completed successfully, fetched 83.6.200.46, and reported SUCCESS Updated your IP on DynDNS. Immediately afterwards, ns0 had advanced to serial 2026152076 but ns1 still returned 83.6.201.191 and serial 2026150504.
Cloudflare DNS currently resolves the correct address, while Google DNS resolves the stale one. This makes the service appear intermittent depending on the resolver.
Could you please investigate and resync the nohost zone on ns1? This does not appear to be a local DynDNS updater, router, reverse-proxy, or Home Assistant issue.
Share relevant logs or error messages
No local DynDNS error: the forced update completed successfully and submitted IPv4 83.6.200.46. The inconsistency is visible in direct authoritative DNS queries immediately after that update.