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
12.1.41.2
How are you able to access your server
The webadmin
SSH
Describe your issue
Hi,
I’ve recently migrated my rasberry with yunohost because I moved out, so my ISP changed my public IP.
I’ve changed this IP in my DNS provider console (OVH). Now for one of my subdomain certificate reniewing process, I see an error in the logs saying the DNS record is different than the server’s IP.
Note that the domain.fr responds with my server so everything’s working fine. Plus I did the DNS entry change about 2 weeks ago so the propagation is done also.
Please also note that I use the OVH API option in yunohost admin UI which is why the certification reniewing process is automatic.
Do I need to update something in yunohost config ?
Thanks for your help 
Share relevant logs or error messages
2026-11-06 06:25:02,729 ERROR yunohost.certmanager.certificate_renew - The DNS records for domain ‘subdomain.domain.fr’ are different to this server’s IP. Please check the ‘DNS records’ (basic) category in the diagnosis for more info. If you recently modified your A record, please wait for it to propagate (some DNS propagation checkers are available online). (If you know what you are doing, use ‘–no-checks’ to turn off these checks.)
If you ping that subdomain, do you get the ip address of your server? Does autodns propose to push changes?
Yup it points to the right direction. I replaced my IP with 0.0.0.0 in the logs but I actually get the new public IP resolved and the subdomain responds.
➜ ~ ping subdomain.domain.fr
PING subdomain.domain.fr (0.0.0.0) 56(84) bytes of data.
64 bytes from 0.0.0.0.isp.domain.fr (0.0.0.0): icmp_seq=1 ttl=48 time=150 ms
64 bytes from 0.0.0.0.isp.domain.fr (0.0.0.0): icmp_seq=2 ttl=48 time=65.4 ms
64 bytes from 0.0.0.0.isp.domain.fr (0.0.0.0): icmp_seq=3 ttl=48 time=84.8 ms
^C
--- subdomain.domain.fr ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 65.401/100.149/150.285/36.321 ms
➜ ~
Auto-DNS seems to want to push changes indeed, maybe I wasn’t supposed to edit the config myself ? But it’s weird because the subdomain on which the bug appears is not identified in the 3 subdomains to edit for ‘A’ entries.
+ subdomain1 A {{ IPv4 }}
+ subdomain2 A {{ IPv4 }}
+ subdomain3 A {{ IPv4 }}
+ subdomain1 MX 10 subdomain1.domain.fr.
+ subdomain2 MX 10 subdomain2.domain.fr.
+ subdomain3 MX 10 subdomain3.domain.fr.
+ _dmarc.subdomain1 TXT "v=DMARC1; p=none"
+ _dmarc.subdomain2 TXT "v=DMARC1; p=none"
+ _dmarc.subdomain3 TXT "v=DMARC1; p=none"
+ subdomain1 TXT "v=spf1 a mx -all"
+ subdomain2 TXT "v=spf1 a mx -all"
+ subdomain3 TXT "v=spf1 a mx -all"
+ mail._domainkey.subdomain1 TXT "v=DKIM1; h=sha256; k=rsa; p={{ key }}"
+ mail._domainkey.subdomain2 TXT "v=DKIM1; h=sha256; k=rsa; p={{ key }}"
+ mail._domainkey.subdomain3 TXT "v=DKIM1; h=sha256; k=rsa; p={{ key }}"
- * AAAA {{ IPv6 }}
- @ AAAA {{ IPv6 }}
- subdomain4 AAAA {{ IPv6 }}
- subdomain5 AAAA {{ IPv6 }}
- subdomain6 AAAA {{ IPv6 }}
- subdomain7 AAAA {{ IPv6 }}
- subdomain8 AAAA {{ IPv6 }}
- subdomain9 AAAA {{ IPv6 }}
- subdomain10 AAAA {{ IPv6 }}
- subdomain11 AAAA {{ IPv6 }}
For the ‘AAAA’ entries, it wants to delete them because since the migration I’ve some troubles with IPv6 from my router which is another problem, I don’t think it’s related.
Try to ping -6 domain
Yes, you should push the proposed changes.