Controller down?

RIPE Atlas
1

My probe 1000568 is losing uptime…

Controller init -p  443 atlas@ctr-dub-sw01.atlas.prod.ripe.net  INIT
...
255 controller INIT exit with error
2

How can I force a controller change? (it’s a SW probe)

3

Hi. We are looking into an issue that is preventing probes connecting to controllers now. I will update you when we have more info.

4

Looks like a DNS issue on your side or routing problem with you network provider.
“ctr-dub-sw01.atlas.prod.ripe.net” resolves on my side as an IPv6-only address (2a13:27c0:1c:d00:26d6:fe95:acb7:2e9a).

If the probe attempts to connect with IPv4, it just fails. And with IPV6, no ping to it replies.

If I lookup “ctr-dub-sw01.atlas.prod.ripe.net” from the Internet (from a website in US), it reports an IPv4 address on Amazon AWS (as “ns-569.awsdns-07.net”, on AS16509) and no IPv6. Apparently this AWS endpoint is not reachable from most ISP’s in Europe.

If I use another DNS lookup in Europe, I see different IPv4 and IPv6 addresses, but no CNAME alias (but there’s a strange TXT record saying: “heritage=external-dns,external-dns/owner=swe-atlas-prod-aws,external-dns/resource=service/ctr-dub-sw01/controller-ssh”; which relates to some “external-dns” managed by RIPE but visibly not accepting connections from various ISPS in Europe that ignore that record, or do not even try to use it).

If I use nslookup from my side on Windows, I get:

Réponse ne faisant pas autorité :
ctr-dub-sw01.atlas.prod.ripe.net ??? unknown type 46 ???
ctr-dub-sw01.atlas.prod.ripe.net text =

    "heritage=external-dns,external-dns/owner=swe-atlas-prod-aws,external-dns/resource=service/ctr-dub-sw01/controller-ssh"

ctr-dub-sw01.atlas.prod.ripe.net ??? unknown type 46 ???
ctr-dub-sw01.atlas.prod.ripe.net internet address = 34.248.40.103
ctr-dub-sw01.atlas.prod.ripe.net internet address = 52.18.43.103
ctr-dub-sw01.atlas.prod.ripe.net internet address = 54.77.167.52
ctr-dub-sw01.atlas.prod.ripe.net ??? unknown type 46 ???
ctr-dub-sw01.atlas.prod.ripe.net AAAA IPv6 address = 2a13:27c0:1c:d02:9e42:ebb1:d908:48d5
ctr-dub-sw01.atlas.prod.ripe.net AAAA IPv6 address = 2a13:27c0:1c:d00:26d6:fe95:acb7:2e9a
ctr-dub-sw01.atlas.prod.ripe.net AAAA IPv6 address = 2a13:27c0:1c:d01:8e75:1394:5074:32f3

What is this “??? unknown type 46 ???”. Is it RFC 4034 DNSSEC Signature (for a DNSSEC-secured record set), alias “RRSIG”, intended as a replacement of SIG (type 24) for use with IPv6 ? Is it really implemented in the probe firmware, or on your AWS-hosted controler servers or configured with its own routers?