Re: les DNS de l'operateur

Oui c'est la piste que je souhaite éclaircir. Mais l'adresse résidentielle ne change pas souvent, voire jamais donc je ne sais pas si c'est le temps de propagation qui est à mettre en cause.

Quelques infos supplémentaires :

(utilisation de ma liaison Sosh/Orange)

 $ dig audionuma.net any
 ; <<>> DiG 9.20.23-1~deb13u1-Debian <<>> audionuma.net any
 ;; global options: +cmd
 ;; Got answer:
 ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10990
 ;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1
 ;; OPT PSEUDOSECTION:
 ; EDNS: version: 0, flags:; udp: 1232
 ; COOKIE: 6eebb59719c10d42010000006a51dbc19241104aa6a9a93d (good)
 ;; QUESTION SECTION:
 ;audionuma.net. IN ANY
 ;; ANSWER SECTION:
 audionuma.net. 300 IN A 128.65.195.180
 audionuma.net. 3600 IN MX 5 mta-gw.infomaniak.ch.
 audionuma.net. 3600 IN TXT "v=spf1 include:spf.infomaniak.ch -all"
 audionuma.net. 86400 IN SOA ns41.infomaniak.com. hostmaster.infomaniak.ch. 2025062602 10800 3600 605800 86400
 audionuma.net. 35868 IN NS ns41.infomaniak.com.
 audionuma.net. 35868 IN NS ns42.infomaniak.com.
 ;; Query time: 36 msec
 ;; SERVER: 192.168.1.1#53(192.168.1.1) (TCP)
 ;; WHEN: Sat Jul 11 07:59:29 CEST 2026
 ;; MSG SIZE rcvd: 271
 $ dig ministock.audionuma.net any
 ; <<>> DiG 9.20.23-1~deb13u1-Debian <<>> ministock.audionuma.net any
 ;; global options: +cmd
 ;; Got answer:
 ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40243
 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
 ;; OPT PSEUDOSECTION:
 ; EDNS: version: 0, flags:; udp: 1232
 ; COOKIE: 065c3271dbae06bc010000006a51dbda3c43a6fcb57ab7d0 (good)
 ;; QUESTION SECTION:
 ;ministock.audionuma.net. IN ANY
 ;; ANSWER SECTION:
 ministock.audionuma.net. 60 IN A 92.129.44.173
 ministock.audionuma.net. 60 IN AAAA 2a01:cb18:115c:4b00:1a5c:d902:91df:6f8
 ;; Query time: 36 msec
 ;; SERVER: 192.168.1.1#53(192.168.1.1) (TCP)
 ;; WHEN: Sat Jul 11 07:59:54 CEST 2026
 ;; MSG SIZE rcvd: 124

Puis utilisation de la liaison SFR (via partage de connexion du tel) :

 $ dig ministock.audionuma.net any
 ;; communications error to 172.20.10.1#53: timed out
 ;; communications error to 172.20.10.1#53: timed out
 ;; communications error to 172.20.10.1#53: timed out
 $ dig audionuma.net any
 ;; communications error to 172.20.10.1#53: timed out
 ;; communications error to 172.20.10.1#53: timed out
 ;; communications error to 172.20.10.1#53: timed out
 $ traceroute audionuma.net
 traceroute to audionuma.net (128.65.195.180), 30 hops max, 60 byte packets
 1 _gateway (172.20.10.1) 3.429 ms 3.238 ms 3.111 ms
 2 * * *
 3 10.2.4.111 (10.2.4.111) 20.362 ms 25.909 ms 25.796 ms
 4 10.203.115.1 (10.203.115.1) 25.673 ms 31.549 ms 31.436 ms
 5 121.149.6.194.rev.sfr.net (194.6.149.121) 31.320 ms 127.149.6.194.rev.sfr.net (194.6.149.127) 31.190 ms 121.149.6.194.rev.sfr.net (194.6.149.121) 31.080 ms
 6 142.146.6.194.rev.sfr.net (194.6.146.142) 44.360 ms 41.003 ms 39.463 ms
 7 sfr.ly1-1.rt.hopus.net (37.77.39.20) 43.854 ms 35.318 ms 35.626 ms
 8 lag-ly1-1.gv1-1.rt.hopus.net (37.77.32.4) 35.466 ms 35.357 ms 35.577 ms
 9 * * *
 10 * * *
 11 * * *
 12 * * *
 13 * * *
 14 * * *
 15 * * *
 16 * * *
 17 * * *
 18 * * *
 19 * * *
 20 * * *
 21 * * *
 22 * * *
 23 * * *
 24 * * *
 25 * * *
 26 * * *
 27 * * *
 28 * * *
 29 * * *
 30 * * *
 $ traceroute ministock.audionuma.net
 traceroute to ministock.audionuma.net (2a01:cb18:115c:4b00:1a5c:d902:91df:6f8), 30 hops max, 80 byte packets
 1 2a02-8440-6505-733d-24ea-6e18-5517-c3ce.rev.sfr.net (2a02:8440:6505:733d:24ea:6e18:5517:c3ce) 3.202 ms 3.013 ms 6.101 ms
 2 * * *
 3 fdff:8440:1111:2015::6f (fdff:8440:1111:2015::6f) 25.163 ms 25.050 ms 29.193 ms
 4 2a02-8400-1502-ec34-0000-0000-0000-0001.rev.sfr.net (2a02:8400:1502:ec34::1) 33.559 ms * *
 5 fc00:0:0:101::637 (fc00:0:0:101::637) 33.230 ms fc00:0:0:101::63b (fc00:0:0:101::63b) 33.122 ms *
 6 * * *
 7 fc00:0:0:101::439 (fc00:0:0:101::439) 23.489 ms * *
 8 2a01:cfc4:0:1800::2 (2a01:cfc4:0:1800::2) 23.109 ms 22.999 ms 22.866 ms
 9 * * *
 10 2a01cb08a00400000193025201020093.ipv6.abo.wanadoo.fr (2a01:cb08:a004:0:193:252:102:93) 21.157 ms 25.795 ms 19.833 ms
 11 2a01cb08a00402130080001001660125.ipv6.abo.wanadoo.fr (2a01:cb08:a004:213:80:10:166:125) 25.600 ms 19.580 ms 19.623 ms
 12 2a01:cb18:115c:4b00:46d4:54ff:fe29:bcd0 (2a01:cb18:115c:4b00:46d4:54ff:fe29:bcd0) 20.812 ms 21.636 ms 19.227 ms
 13 * * *
 14 * * *
 15 * * *
 16 * * *
 17 * * *
 18 * * *
 19 * * *
 20 * * *
 21 * * *
 22 * * *
 23 * * *
 24 * * *
 25 * * *
 26 * * *
 27 * * *
 28 * * *
 29 * * *
 30 * * *

Je vois que y'a de l'IP v6 qui apparaît mais je suis bien en peine de savoir pourquoi et quel est l'impact potentiel.

Pour info, le domaine est enregistré chez Infomaniak et c'est ddclient qui tourne sur le RPi et utlise l'api de Infomaniak pour les màj adresse IP. Sur l'interface Infomaniak les dernières modifications dyndns (en IP v4 et v6) sur le sous-domaine datent de juin 2025.