[GH-ISSUE #435] Problem with ipv6 update #315

New issue

Closed

opened 2026-02-26 10:30:46 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 10:30:46 +03:00

Owner

Originally created by @skycrash on GitHub (Jul 15, 2019).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/435

A few weeks I'm having problem to update ipv6 .

Timeout to connect:
curl -6 https://xxxx.nsupdate.info:00000@ipv6.nsupdate.info/nic/update

I test from many others networks and not working. Anybody with this problem too ?

ping6 ipv6.nsupdate.info

PING ipv6.nsupdate.info(2a01:4f8:a1:6e:0:80:0:1) 56 data bytes

Originally created by @skycrash on GitHub (Jul 15, 2019). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/435 A few weeks I'm having problem to update ipv6 . Timeout to connect: curl -6 https://xxxx.nsupdate.info:00000@ipv6.nsupdate.info/nic/update I test from many others networks and not working. Anybody with this problem too ? # ping6 ipv6.nsupdate.info PING ipv6.nsupdate.info(2a01:4f8:a1:6e:0:80:0:1) 56 data bytes

kerem closed this issue

2026-02-26 10:30:46 +03:00

kerem commented

2026-02-26 10:30:47 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Jul 15, 2019):

$ ping6 ipv6.nsupdate.info
PING ipv6.nsupdate.info(2a01:4f8:a1:6e:0:80:0:1) 56 data bytes
64 bytes from 2a01:4f8:a1:6e:0:80:0:1: icmp_seq=1 ttl=56 time=22.6 ms
64 bytes from 2a01:4f8:a1:6e:0:80:0:1: icmp_seq=2 ttl=56 time=58.5 ms
64 bytes from 2a01:4f8:a1:6e:0:80:0:1: icmp_seq=3 ttl=56 time=27.4 ms

Guess the routing from your place to our server is broken somewhere, check traceroute6:

# traceroute6 ipv6.nsupdate.info
traceroute to ipv6.nsupdate.info (2a01:4f8:a1:6e:0:80:0:1) from 2001:470:1f0b:c63:29c:2ff:fea2:fc73, 30 hops max, 24 byte packets
 1  2001:470:1f0b:c63:c225:6ff:fe2a:f230 (2001:470:1f0b:c63:c225:6ff:fe2a:f230)  1.517 ms  0.814 ms  0.897 ms
 2  * * tunnel374590.tunnel.tserv6.fra1.ipv6.he.net (2001:470:1f0a:c63::1)  19.378 ms
 3  * 10ge3-18.core1.fra1.he.net (2001:470:0:69::1)  14.977 ms  12.298 ms
 4  decix2-gw.hetzner.de (2001:7f8::616c:0:2)  17.467 ms  14.357 ms  23.54 ms
 5  core12.nbg1.hetzner.com (2a01:4f8:0:3::f6)  39.974 ms  23.217 ms  27.164 ms
 6  ex9k1.dc1.nbg1.hetzner.com (2a01:4f8:0:3::162)  26.282 ms  23.362 ms  22.925 ms
 7  s1n.thinkmo.de (2a01:4f8:a1:6e::1)  33.839 ms  23.568 ms  22.353 ms
 8  s1n.thinkmo.de (2a01:4f8:a1:6e::1)  29.277 ms  37.541 ms  23.955 ms

@ThomasWaldmann commented on GitHub (Jul 15, 2019): ``` $ ping6 ipv6.nsupdate.info PING ipv6.nsupdate.info(2a01:4f8:a1:6e:0:80:0:1) 56 data bytes 64 bytes from 2a01:4f8:a1:6e:0:80:0:1: icmp_seq=1 ttl=56 time=22.6 ms 64 bytes from 2a01:4f8:a1:6e:0:80:0:1: icmp_seq=2 ttl=56 time=58.5 ms 64 bytes from 2a01:4f8:a1:6e:0:80:0:1: icmp_seq=3 ttl=56 time=27.4 ms ``` Guess the routing from your place to our server is broken somewhere, check traceroute6: ``` # traceroute6 ipv6.nsupdate.info traceroute to ipv6.nsupdate.info (2a01:4f8:a1:6e:0:80:0:1) from 2001:470:1f0b:c63:29c:2ff:fea2:fc73, 30 hops max, 24 byte packets 1 2001:470:1f0b:c63:c225:6ff:fe2a:f230 (2001:470:1f0b:c63:c225:6ff:fe2a:f230) 1.517 ms 0.814 ms 0.897 ms 2 * * tunnel374590.tunnel.tserv6.fra1.ipv6.he.net (2001:470:1f0a:c63::1) 19.378 ms 3 * 10ge3-18.core1.fra1.he.net (2001:470:0:69::1) 14.977 ms 12.298 ms 4 decix2-gw.hetzner.de (2001:7f8::616c:0:2) 17.467 ms 14.357 ms 23.54 ms 5 core12.nbg1.hetzner.com (2a01:4f8:0:3::f6) 39.974 ms 23.217 ms 27.164 ms 6 ex9k1.dc1.nbg1.hetzner.com (2a01:4f8:0:3::162) 26.282 ms 23.362 ms 22.925 ms 7 s1n.thinkmo.de (2a01:4f8:a1:6e::1) 33.839 ms 23.568 ms 22.353 ms 8 s1n.thinkmo.de (2a01:4f8:a1:6e::1) 29.277 ms 37.541 ms 23.955 ms ```

kerem commented

2026-02-26 10:30:47 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Jul 15, 2019):

Also, curl is not a good way to update your IP, you should use a dyndns update client so you are not using way more resources than necessary on the server side.

@ThomasWaldmann commented on GitHub (Jul 15, 2019): Also, `curl` is not a good way to update your IP, you should use a dyndns update client so you are not using way more resources than necessary on the server side.

kerem commented

2026-02-26 10:30:47 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Dec 27, 2019):

Guess this is resolved.

@ThomasWaldmann commented on GitHub (Dec 27, 2019): Guess this is resolved.