Checkipv6.dedyn.io not pingable

dynDNS at dedyn.io
1

Since yesterday, checkipv6.dedyn.io is not pingable and returns not the IPV6 set in desec.io

IPV4 works fine

ping4 checkipv4.dedyn.io
PING checkipv4.dedyn.io (88.99.64.5) 56(84) bytes of data.
64 bytes from digga.desec.io (88.99.64.5): icmp_seq=1 ttl=58 time=16.2 ms
64 bytes from digga.desec.io (88.99.64.5): icmp_seq=2 ttl=58 time=14.3 ms

but not checkipv6:

ping6 checkipv6.dedyn.io
PING checkipv6.dedyn.io (2a01:4f8:10a:1044:deec:642:ac10:80) 56 data bytes

— checkipv6.dedyn.io ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3123ms

Outage status page shows all working fine ….

1 Like
2

I have it scripted, thats not working

$ ping4 -c 1 -w 5 -q checkipv4.dedyn.io
PING checkipv4.dedyn.io (88.99.64.5) 56(84) bytes of data.

— checkipv4.dedyn.io ping statistics —
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 15.881/15.881/15.881/0.000 ms

ping6 -c 1 -w 5 -q checkipv6.dedyn.io
PING checkipv6.dedyn.io (2a01:4f8:10a:1044:deec:642:ac10:80) 56 data bytes

— checkipv6.dedyn.io ping statistics —
5 packets transmitted, 0 received, 100% packet loss, time 4129ms

3

I can confirm that we’re having ipv6 issues at desec.io. it looks like it’s caused by a docker update. We’re working to fix it, stay tuned.

Nils

2 Likes
4

Hi un99know99,

Thank for your report!

The issue was indeed cause by Docker update, where the network configuration syntax unexpectedly changed (although it was a minor upgrade). Unfortunately, our test suite didn’t catch this particular case, because things were working over IPv4.

We’ve fixed the problem, and will extend our tests to cover this in the future.

Details: API and web unreachable via IPv6 | deSEC Status

We’re sorry this hasn’t been caught earlier. In general, it’s best to report technical issues directly to support, so we’ll see it earlier.

Stay secure,
Peter

3 Likes