Using Yunohost for domain - fails repeatedly - suggestions welcomed

Support
1

What type of hardware are you using: Old laptop or computer
What YunoHost version are you running: 12.0.17 (stable)
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 ?: No

Describe your issue

I have a mail server (SOGo) set up on a duckdns domain but I often get errors due to dns configuration errors or omissions. I thought the clever answer would be to use a Yunohost provided DNS address for this app thus ensuring it was all configured automatically (and correctly) rather than rely on my bumbling about. However, whenever I try to setup my shiny new domain it fails and from the log I’m struggling to spot any obvious error. Can anyone have a quick peek at the attached and provide any pointers?
Thanks.

Share relevant logs or error messages

args:
  domain: domain2.tld
  force: false
ended_at: 2025-06-13 12:11:47.200499
error: Could not update IP address to DynDNS
interface: api
operation: dyndns_update
parent: null
related_to:
- - domain
  - domain2.tld
- - domain
  - domain2.tld
started_at: 2025-06-13 12:11:46.938301
success: false
yunohost_version: 12.0.17

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

2025-06-13 13:11:46,947: INFO - Updated needed, going on...
2025-06-13 13:11:46,953: DEBUG - Reusing IPv4 from cache: xx.xx.xx.xx
2025-06-13 13:11:46,953: DEBUG - Reusing IPv6 from cache: None
2025-06-13 13:11:47,146: DEBUG - Formating result in 'export' mode
2025-06-13 13:11:47,170: DEBUG - Now pushing new conf to DynDNS host...
2025-06-13 13:11:47,171: DEBUG - id 5535
opcode UPDATE
rcode NOERROR
flags 
;ZONE
ynh.fr. IN SOA
;PREREQ
;UPDATE
domain2.tld. ANY ANY
domain2.tld. ANY ANY
domain2.tld. ANY ANY
*.domain2.tld. ANY ANY
domain2.tld. ANY ANY
domain2.tld. 3600 IN A xx.xx.xx.xx
domain2.tld. 3600 IN MX 10 otd488r
domain2.tld. 3600 IN TXT "v=spf1 a mx -all"
*.domain2.tld. 3600 IN A xx.xx.xx.xx
domain2.tld. 3600 IN CAA 0 issue "letsencrypt.org"
;ADDITIONAL
2025-06-13 13:11:47,194: ERROR - id 5535
opcode UPDATE
rcode FORMERR
flags QR
;ZONE
ynh.fr. IN SOA
;PREREQ
;UPDATE
;ADDITIONAL
2

You could also share the diagnosis link.
You can have only one yunohost domain on your server.

3

Ooo I wasn’t aware of the link. Is this what you mean:- https://paste.yunohost.org/raw/abetomazeh ?
I have tried to create a domain in the past but have no others in use at the moment from Yunohost. Do you mean that Yunohost may remember my previous attempt and hence count that as my one domain? How can I ‘erase’ any old domain attempts? Your advice is appreciated.
Thanks.

4

I’ve just spotted a ‘sticky’ thread that looks to be a place to request the deletion of old free domains. Unfortunately I cant remember the name of my failed old domain names. Do I need to submit a request here? :- Nohost domain recovery - Suppression de domaine en nohost.me, noho.st et ynh.fr - #6 by domos

5

Darn it. I see that sticky post is no longer monitored. I’m not sure how to progress now. Any pointers?

6

I tried the CLI with the below and got the subsequent response:-

yunohost domain dyndns subscribe otd488r.ynh.fr -p password
Error: You have already subscribed to a DynDNS domain

It appears that my dim and distant attempt is the problem. How on earth can I remove the old domain?

7

What’s the output of yunohost domain list ? Is there a yunohost domain?

It’s still monitored, but it’s time consuming, so requests are handleded when admins have time.

8

ahh, OK. I shall be patient , thanks.

9

I’ll try that command later. cheers.

10

The command only showed my five duckdns domains and the one new one I am trying to create otd488r.ynh.fr.

11

I tried to clear it all out and it looks like they have all gone but it still fails to create the new domain. Wierdly at the same time I appear to have a related cron job running every 10 minutes that fails and sends me an email related to Dyndns. See below.

Cron root@kfz2291 : YunoHost DynDNS update; sleep $((RANDOM%60)); ! ping -q -W5 -c1 ip.yunohost.org >/dev/null 2>&1 || test -e /var/run/moulinette_yunohost.lock || yunohost dyndns update >> /dev/null

ERROR No domain registered with DynDNS

12

What’s the output of sudo ls /etc/yunohost/dyndns/ ?

13

Interestingly, nothing. That directory is empty.

14

I tried again to create the domain it failed again, see attached.
https://paste.yunohost.org/raw/rivureyibe
Thx.

15

And now I’m receiving an email from Cron every 10 mins with the same text but different random error codes example below.
ERROR id 1466
opcode UPDATE
rcode FORMERR
flags QR
;ZONE
nohost.me. IN SOA
;PREREQ
;UPDATE
;ADDITIONAL
ERROR Could not update IP address to DynDNS

16

I have noticed an issue on the daily analysis that may be related. It complains that nsswitch.conf has been modified. I know I haven’t touched it intentionally. When I look at the differences I see the below.
nsswitch:
applied:
pending:
/etc/nsswitch.conf:
diff: @@ -5,7 +5,7 @@
shadow: files ldap
gshadow: files

-hosts: files myhostname dns
+hosts: files myhostname mdns4_minimal [NOTFOUND=return] dns
networks: files

If I try to run the force command to rest the file it fails, the log is here:- https://paste.yunohost.org/raw/fawofugori
Could the two issues be related? They seem to both relate to DNS.

17 
args:
  dry_run: false
  force: false
  list_pending: false
  names:
  - "nsswitch\_--force"
  with_diff: false
ended_at: 2025-06-15 08:53:01.942305
error: 'Could not regenerate the configuration for category(s): '

nsswitch\_--force: afaik that command doesn’t exist. Try instead sudo yunohost tools regen-conf nsswitch

18

cheers. I fixed that command. I used the parameter -f rather than the Yunohost suggested --force and it worked. Will try creating a new dyndns entry to see if that now works.

19

It was not the problem.

20

Sadly, no, the original issue is still present. I cleared it all down and checked that no yunohost dydns domains were present, then I tried to create a new one again. It failed. Here is the log. https://paste.yunohost.org/raw/neziwozice
I’m really struggling with this one.