I was trying to query the DNS instances in the anycast directly, to see how fast the replication is, see:
I found the instances at desec-automation/hosts/all.yml at main · desec-io/desec-automation · GitHub.
Which all can be queried over IPv4, but only .a.desec.io works for me over IPv6:
echo @{ams,dfw,sao,fra,hkg,jnb,syd}-1.a.desec.io \
| xargs -P7 -n1 dig +tries=1 -6 +short TXT test.onverwijld.nl
"alice"
"alice"
"alice"
"alice"
"alice"
"alice"
"alice"
echo @{dxb,fra,lax,sin,lga,lhr,scl,tyo}-1.c.desec.io \
| xargs -P8 -n1 dig +tries=1 -6 +short TXT test.onverwijld.nl
;; communications error to 2403:2500:400:20::635#53: timed out
;; no servers could be reached
;; communications error to 2a00:dd80:20::d91#53: timed out
;; no servers could be reached
;; communications error to 2607:f740:c::6f9#53: timed out
;; no servers could be reached
;; communications error to 2607:f740:f::8e9#53: timed out
;; no servers could be reached
;; communications error to 2607:f740:56:10::3e9#53: timed out
;; no servers could be reached
;; communications error to 2a00:dd80:3f:100::502#53: timed out
;; no servers could be reached
;; communications error to 2403:2500:300::480#53: timed out
;; communications error to 2a00:dd80:3a::21e#53: timed out
;; no servers could be reached
;; no servers could be reached
While querying the IPv6 anycast ns2.desec.org has no issues.
Is this a deliberate difference or due to a software configuration difference?