Old configuration DNS from old domain nanme still here?

Support
1

My YunoHost server

Hardware: Old laptop or computer at home with VPN
YunoHost version: 4.3.6.3
I have access to my server : Through SSH | through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no

Failed to resolve A for domain.ynh.fr

It makes long time I have change this domain name and use another domain.fr.
in the domain list, I haven’t no more this domain…
I have received this mail message:

Cron root@domain : 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
Failed to resolve A for domain.ynh.fr

I remember I have signaled to erase the domain.ynh.fr (where is this page for these request ?). But it seems hardcoded somewhere ???

Perhaps it is not a strong problem…

2

You should do that to fix the problem ().

rm -Rf /etc/yunohost/dyndns
yunohost tools regen-conf yunohost

NB: after yunohost 11.1, it should not be needed anymore to do that thanks to the work of theo (currently in internship inside ReflexLibre) and working on a PR that fix this kind of issue with dyndns domains: Allowing to unsubscribe from DynDNS by theo-is-taken · Pull Request #1472 · YunoHost/yunohost · GitHub

3

Thanks !

4

Ok, since this operations, I have a new issue:
[ERROR] Le service yunomdns est failed
I have try ‘yunohost service restart yunomdns’ and ‘yunohost service log yunomdns’ and got this:

 - juil. 10 18:35:03 systemd[1]: Started YunoHost mDNS service.
  - juil. 10 18:35:03 yunomdns[572]: Traceback (most recent call last):
  - juil. 10 18:35:03 yunomdns[572]:   File "/usr/bin/yunomdns", line 170, in <module>
  - juil. 10 18:35:03 yunomdns[572]:     sys.exit(0 if main() else 1)
  - juil. 10 18:35:03 yunomdns[572]:   File "/usr/bin/yunomdns", line 57, in main
  - juil. 10 18:35:03 yunomdns[572]:     with open("/etc/yunohost/mdns.yml", "r") as f:
  - juil. 10 18:35:03 yunomdns[572]: PermissionError: [Errno 13] Permission denied: '/etc/yunohost/mdns.yml'
  - juil. 10 18:35:03 systemd[1]: yunomdns.service: Main process exited, code=exited, status=1/FAILURE
  - juil. 10 18:35:03 systemd[1]: yunomdns.service: Failed with result 'exit-code'.
  - juil. 10 21:02:24 systemd[1]: Started YunoHost mDNS service.
  - juil. 10 21:02:24 yunomdns[3651]: Traceback (most recent call last):
  - juil. 10 21:02:24 yunomdns[3651]:   File "/usr/bin/yunomdns", line 170, in <module>
  - juil. 10 21:02:24 yunomdns[3651]:     sys.exit(0 if main() else 1)
  - juil. 10 21:02:24 yunomdns[3651]:   File "/usr/bin/yunomdns", line 57, in main
  - juil. 10 21:02:24 yunomdns[3651]:     with open("/etc/yunohost/mdns.yml", "r") as f:
  - juil. 10 21:02:24 yunomdns[3651]: PermissionError: [Errno 13] Permission denied: '/etc/yunohost/mdns.yml'
  - juil. 10 21:02:24 systemd[1]: yunomdns.service: Main process exited, code=exited, status=1/FAILURE
  - juil. 10 21:02:24 systemd[1]: yunomdns.service: Failed with result 'exit-code'.

Ok I found a solution herre: Service yunomdns is broken - #4 by metyun

5

Hi, with a server upgraded to Yunohost 11 bullseye hosted on a vps OVH, I still have this message

La résolution DNS semble fonctionner, mais il semble que vous utilisez un /etc/resolv.conf personnalisé.

Le fichier /etc/resolv.conf doit être un lien symbolique vers /etc/resolvconf/run/resolv.conf lui-même pointant vers 127.0.0.1 (dnsmasq). Si vous souhaitez configurer manuellement les résolveurs DNS, veuillez modifier /etc/resolv.dnsmasq.conf.

Perhaps I have to delete the symlink ??
ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 31 Jul 25 20:02 /etc/resolv.conf -> /etc/resolvconf/run/resolv.conf

6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.