Could not update IP address to DynDNS

,

Bonjour,

Sur un serveur Lime 1 à jour, sans anomalies dans les diagnostics, j’ai le message d’erreur suivant :
; Communication with 2001:910:1410::1#53 failed: operation canceled update failed: FORMERR Could not update IP address to DynDNS

Ce message est apparu le 20/09 après un autre message
Failed to resolve dyndns.yunohost.org et j’en ai bientôt 50 (!) qui arrivent parfois à raison de plusieurs en une heure.

Je ne sais pas ce que veut dire ce message, ni comment résoudre ce problème.

Merci pour votre aide !

What does mean :
; Communication with 2001:910:1410::1#53 failed: operation canceled update failed: FORMERR Could not update IP address to DynDNS
I’ve got that message on a Lime 1 up to date server.

Thanks for your kind help !

Try to diagnose your network by hand:

ping 9.9.9.9
dig A wikipedia.org
dig A dyndns.yunohost.org
ping6 wikipedia.org
ping dyndns.yunohost.org
ping6 dyndns.yunohost.org

Tout ping !
Le dernier message d’erreur est arrivé hier à 18h43…

Tout semble fonctionner sans anomalie, mais rien ne me permet de penser que ça ne se reproduira pas.

Vraiment bizarre…

:thinking:

Quelle pourrait être la source d’un tel problème?

Il n’a pas fallu attendre trop longtemps pour voir reparaître l’erreur à 14h12 aujourd’hui.

Et tout ping sans problème…
:thinking: :face_with_monocle:

J’ai reçu le même message à raison de 5 fois par heure de 1 à 7h du matin, puis plus rien jusqu’à 17h23. Et là, 3 messages en 20 mn !
; Communication with 2001:910:1410::1#53 failed: operation canceled update failed: FORMERR Could not update IP address to DynDNS

Quelqu’un saurait-il de quoi il s’agit ?

Merci !

# ping 9.9.9.9 PING 9.9.9.9 (9.9.9.9) 56(84) bytes of data. 64 bytes from 9.9.9.9: icmp_seq=1 ttl=54 time=17.8 ms`

Mais

ping6 wikipedia.org ou ping6 dyndns.yunohost.org
n’aboutissent pas.

# dig A dyndns.yunohost.org

; <<>> DiG 9.11.5-P4-5.1+deb10u5-Debian <<>> A dyndns.yunohost.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21216 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;dyndns.yunohost.org. IN A

;; ANSWER SECTION: dyndns.yunohost.org. 1492 IN A 80.67.172.144

;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sat Sep 25 15:55:09 UTC 2021 ;; MSG SIZE rcvd: 64

Est-ce que ça peut aider pour diagnostiquer?
Un problème d’ IPv6?

(Sorry for my lack of French!)

The Yunohost of one of my daughters loses IPv6 connectivity. I made a script (including some other stuff) that I run after boot, and when needed, to add a route for IPv6:

ip -6 route add default via fe80::2e3a:fdff:fe82:3f23 dev eth0

The global IPv6 gives no connection when added in a route.

Another problem I have with IPv6, is that there are 3 adresses:

  1. Automatic (SLAAC?) adress, 2001:985::MAC scope global dynamic mngtmpaddr
  2. The configured IPv6, 2001:985::…
  3. Automatic local link, fe80::…

Yunohost diagnosis expects no. 2, but the SLAAC reappears on top every time and throws the diagnosis in disarray. Maybe it causes other problems as well.

How does your ip addr and ip -6 route look like?

Hi @wbk ,

I don’t have the error message since 2 days. I don’t know why.
:thinking:
ip -6 route gives :

::1 dev lo proto kernel metric 256 pref medium
2001:913:1fff:ffff::/64 dev tun0 proto kernel metric 256 pref medium
2000::/3 dev tun0 metric 1024 pref medium
fe80::42:acab dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev tun0 proto kernel metric 256 pref medium
fe80::/64 dev wlan0 proto kernel metric 256 pref medium

Hi,
I just had the error message few minutes ago !

No problem with the ping and dig commands. ip -6 route gives the same as yesterday and

ip addr gives :

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 36:b0:ca:1a:f7:54 brd ff:ff:ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 02:10:09:02:d6:54 brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.78/24 brd 192.168.178.255 scope global dynamic eth0
       valid_lft 74963sec preferred_lft 74963sec
    inet6 fe80::42:acab/128 scope link 
       valid_lft forever preferred_lft forever
    inet6 fe80::10:9ff:fe02:d654/64 scope link 
       valid_lft forever preferred_lft forever
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 02:e1:b0:60:91:00 brd ff:ff:ff:ff:ff:ff
    inet 10.0.242.1/24 scope global wlan0
       valid_lft forever preferred_lft forever
    inet6 fe80::e1:b0ff:fe60:9100/64 scope link 
       valid_lft forever preferred_lft forever
6: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 100
    link/none 
    inet 80.67.181.139/25 brd 80.67.181.255 scope global tun0
       valid_lft forever preferred_lft forever
    inet6 2001:913:1fff:ffff::b:d0fc/64 scope global 
       valid_lft forever preferred_lft forever
    inet6 fe80::d0ce:2651:2fc:1999/64 scope link stable-privacy 
       valid_lft forever preferred_lft forever

I don’t understand anything.
:crazy_face:

Might be a connectivity error with your VPN provider ?

I will ask them.

Thanks !

Finally, I have a better explanation: normally your ip should not change with this kind of VPN. But i suppose your VPN ipv6 switch between 2 values, cause your ISP push ipv6 through your vpn and give you a .cube with the ipv6 prefix fill too.

So i suggest you to empty the “ipv6 prefix” in the vpnadmin interface and save the change.

1 Like

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