Dyndns Update Failed

Mon serveur YunoHost

Matériel: VPS acheté en ligne
Version de YunoHost: 11.1.18
J’ai accès à mon serveur : En SSH | Par la webadmin
Êtes-vous dans un contexte particulier ou avez-vous effectué des modifications particulières sur votre instance ? : oui
Si oui, expliquer:
J’ai migré le serveur sur un vps en faisant un backup/restore sur la nouvell infra. Avant il était hébergé chez moi sur un optiplex 7040M.

Description du problème

Bonjour,

Depuis la migration de mon instance yunohost de chez moi vers un vps, le dyndns ne focntionne plus. Je reçois beaucoup de mail qui me dit “Failed to resolve IPv4/IPv6 for [‘ns0.yunohost.org’, ‘ns1.yunohost.org’]”. J’ai reduis la quantité de mail pour pas me faire blacklist par les anti-spam avec la modification du lancement de la tache cron.
L’ipv6 est désactivé sur le serveur plus simple pour moi.
je ne vois pas très bien ce qu’il se passe.
Merci pour votre temps !

yunohost dyndns update --debug
129  DEBUG initializing base actions map parser for cli
130  DEBUG loading actions map
132  DEBUG building parser...
133  DEBUG building parser took 0.002s
134  DEBUG acquiring lock...
145  DEBUG lock has been acquired
318  DEBUG loading python module yunohost.dyndns took 0.174s
319  DEBUG processing action [806003.1]: yunohost.dyndns.update with args={'domain': None, 'force': False, 'dry_run': False}
333  DEBUG Fetching IP from https://ip.yunohost.org 
336  DEBUG Starting new HTTPS connection (1): ip.yunohost.org:443
404  DEBUG https://ip.yunohost.org:443 "GET / HTTP/1.1" 200 13
406  DEBUG IP fetched: xxx.xxx.xxx.xxx
411  DEBUG No default route for IPv6, so assuming there's no IP address for that version
411  DEBUG IP fetched: None
412  DEBUG Building zone update ...
22449 DEBUG action [806003.1] executed in 22.130s
22450 DEBUG lock has been released
22450 ERROR Failed to resolve IPv4/IPv6 for ['ns0.yunohost.org', 'ns1.yunohost.org'] ?

Une autre erreur.

=================================
DNS records (dnsrecords)
=================================

[ERROR] Some DNS records are missing or incorrect for domain danteh.ynh.fr (category basic)
  - This domain's DNS configuration should automatically be managed by YunoHost. If that's not the case, you can try to force an update using 'yunohost dyndns update --force'.
  - According to the recommended DNS configuration, you should add a DNS record with the following info.
    Type: A
    Name: @
    Value: xxx.xxx.xxx.xxx

[ERROR] Some DNS records are missing or incorrect for domain danteh.ynh.fr (category mail)
  - This domain's DNS configuration should automatically be managed by YunoHost. If that's not the case, you can try to force an update using 'yunohost dyndns update --force'.
  - According to the recommended DNS configuration, you should add a DNS record with the following info.
    Type: MX
    Name: @
    Value: 10 danteh.ynh.fr.
  - According to the recommended DNS configuration, you should add a DNS record with the following info.
    Type: TXT
    Name: @
    Value: "v=spf1 a mx -all"
  - According to the recommended DNS configuration, you should add a DNS record with the following info.
    Type: TXT
    Name: mail._domainkey
    Value: "v=DKIM1; h=sha256; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbHC7xXHkl28+E/sFQcBwEysmvxSnJ3niYHe22GhXOj0dPBD5OB9//KqryNJ6nG6UERg6fCzNR+ghT2iNTDaY9ODhOAaxIbPfzDzIRyBWahEnoHNBV5WLNxZd59gaxT2CmPecmspc2EuQ9PkhLEocjFsbMo6CL0gUFdhwiS4krwQIDAQAB"
  - According to the recommended DNS configuration, you should add a DNS record with the following info.
    Type: TXT
    Name: _dmarc
    Value: "v=DMARC1; p=none"

[WARNING] Some DNS records are missing or incorrect for domain danteh.ynh.fr (category xmpp)
  - This domain's DNS configuration should automatically be managed by YunoHost. If that's not the case, you can try to force an update using 'yunohost dyndns update --force'.
  - According to the recommended DNS configuration, you should add a DNS record with the following info.
    Type: SRV
    Name: _xmpp-client._tcp
    Value: 0 5 5222 danteh.ynh.fr.
  - According to the recommended DNS configuration, you should add a DNS record with the following info.
    Type: SRV
    Name: _xmpp-server._tcp
    Value: 0 5 5269 danteh.ynh.fr.
  - According to the recommended DNS configuration, you should add a DNS record with the following info.
    Type: CNAME
    Name: muc
    Value: danteh.ynh.fr.
  - According to the recommended DNS configuration, you should add a DNS record with the following info.
    Type: CNAME
    Name: pubsub
    Value: danteh.ynh.fr.
  - According to the recommended DNS configuration, you should add a DNS record with the following info.
    Type: CNAME
    Name: vjud
    Value: danteh.ynh.fr.
  - According to the recommended DNS configuration, you should add a DNS record with the following info.
    Type: CNAME
    Name: xmpp-upload
    Value: danteh.ynh.fr.

[WARNING] Some DNS records are missing or incorrect for domain danteh.ynh.fr (category extra)
  - This domain's DNS configuration should automatically be managed by YunoHost. If that's not the case, you can try to force an update using 'yunohost dyndns update --force'.
  - According to the recommended DNS configuration, you should add a DNS record with the following info.
    Type: A
    Name: *
    Value: xxx.xxx.xxx.xxx
  - According to the recommended DNS configuration, you should add a DNS record with the following info.
    Type: CAA
    Name: @
    Value: 0 issue "letsencrypt.org"

[WARNING] Unable to check the expiration date for some domains
  - The domain danteh.ynh.fr doesn't exist in WHOIS database or is expired!

Mouai ok … Qu’est-ce que ça raconte si tu fais ping -c3 ns0.yunohost.org sur ton serveur ?

ça passe
ping -c3 ns0.yunohost.org
PING ns0.yunohost.org (80.67.172.144) 56(84) bytes of data.
64 bytes from yunohost.org (80.67.172.144): icmp_seq=1 ttl=60 time=1.19 ms
64 bytes from yunohost.org (80.67.172.144): icmp_seq=2 ttl=60 time=1.31 ms
64 bytes from yunohost.org (80.67.172.144): icmp_seq=3 ttl=60 time=1.31 ms

Juste pour info ça me donne bien l’ip publique là je l’ai juste caché ^^

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