<![CDATA[@jerry Sorry to bother you.]]>@jerry Sorry to bother you. Are you aware of any issues with DNS for infosec.exchange. For some reason I am unable to resolve on my unbound recursive resolver.
If I try to resolve it with any other DNS provider Quad9 etc it resolves.

Though if I try to query from the root serves backwards I start to get the same errors:
;; communications error to 199.247.152.53#53: timed out

I may be being dumb and going about investigating this the wrong way with my limited DNS knowledge.

Just wondered if you knew of any issues with the root nameservers fro the exchange TDL.

Sample of dig commands on the various nameserves:
dig infosec.exchange @127.0.0.1 -p 5335
;; communications error to 127.0.0.1#5335: timed out
;; communications error to 127.0.0.1#5335: timed out
;; communications error to 127.0.0.1#5335: timed out

; <<>> DiG 9.20.21-1~deb13u1-Debian <<>> infosec.exchange @127.0.0.1 -p 5335
;; global options: +cmd
;; no servers could be reached

dig infosec.exchange @192.203.230.10

; <<>> DiG 9.20.21-1~deb13u1-Debian <<>> infosec.exchange @192.203.230.10
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21116
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 6, ADDITIONAL: 13
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1472
;; QUESTION SECTION:
;infosec.exchange. IN A

;; AUTHORITY SECTION:
exchange. 172800 IN NS v0n0.nic.exchange.
exchange. 172800 IN NS v0n1.nic.exchange.
exchange. 172800 IN NS v0n2.nic.exchange.
exchange. 172800 IN NS v0n3.nic.exchange.
exchange. 172800 IN NS v2n0.nic.exchange.
exchange. 172800 IN NS v2n1.nic.exchange.

;; ADDITIONAL SECTION:
v0n0.nic.exchange. 172800 IN A 65.22.28.14
v0n0.nic.exchange. 172800 IN AAAA 2a01:8840:1e::14
v0n1.nic.exchange. 172800 IN A 65.22.29.14
v0n1.nic.exchange. 172800 IN AAAA 2a01:8840:1f::14
v0n2.nic.exchange. 172800 IN A 65.22.30.14
v0n2.nic.exchange. 172800 IN AAAA 2a01:8840:20::14
v0n3.nic.exchange. 172800 IN A 161.232.14.14
v0n3.nic.exchange. 172800 IN AAAA 2a01:8840:f8::14
v2n0.nic.exchange. 172800 IN A 65.22.31.14
v2n0.nic.exchange. 172800 IN AAAA 2a01:8840:21::14
v2n1.nic.exchange. 172800 IN A 161.232.15.14
v2n1.nic.exchange. 172800 IN AAAA 2a01:8840:f9::14

;; Query time: 11 msec
;; SERVER: 192.203.230.10#53(192.203.230.10) (UDP)
;; WHEN: Tue May 12 14:58:04 BST 2026
;; MSG SIZE rcvd: 427

dig infosec.exchange @65.22.28.14

; <<>> DiG 9.20.21-1~deb13u1-Debian <<>> infosec.exchange @65.22.28.14
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49297
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;infosec.exchange. IN A

;; AUTHORITY SECTION:
infosec.exchange. 3600 IN NS ns3.dnsimple-edge.io.
infosec.exchange. 3600 IN NS ns4.dnsimple-edge.org.
infosec.exchange. 3600 IN NS ns1.dnsimple-edge.com.
infosec.exchange. 3600 IN NS ns2.dnsimple-edge.net.

;; Query time: 123 msec
;; SERVER: 65.22.28.14#53(65.22.28.14) (UDP)
;; WHEN: Tue May 12 14:58:39 BST 2026
;; MSG SIZE rcvd: 184

dig infosec.exchange @ns1.dnsimple-edge.net
;; communications error to 199.247.152.53#53: timed out
;; communications error to 199.247.152.53#53: timed out
;; communications error to 199.247.152.53#53: timed out
;; UDP setup with 2620:111:8004::53#53(2620:111:8004::53) for infosec.exchange failed: network unreachable.
;; no servers could be reached

dig infosec.exchange @9.9.9.9

; <<>> DiG 9.20.21-1~deb13u1-Debian <<>> infosec.exchange @9.9.9.9
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37292
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;infosec.exchange. IN A

;; ANSWER SECTION:
infosec.exchange. 2800 IN A 151.101.195.52
infosec.exchange. 2800 IN A 151.101.131.52
infosec.exchange. 2800 IN A 151.101.3.52
infosec.exchange. 2800 IN A 151.101.67.52

;; Query time: 19 msec
;; SERVER: 9.9.9.9#53(9.9.9.9) (UDP)
;; WHEN: Tue May 12 15:04:59 BST 2026
;; MSG SIZE rcvd: 109

]]>https://board.circlewithadot.net/topic/fa74cb08-1bc4-413f-acf1-86e0308a2532/@jerry-sorry-to-bother-you.RSS for NodeFri, 15 May 2026 07:11:00 GMTTue, 12 May 2026 14:05:48 GMT60<![CDATA[Reply to @jerry Sorry to bother you. on Tue, 12 May 2026 14:44:41 GMT]]>@aircooledcafe I'm not aware of any problems - I host dns with dnsimple and their status page isn't showing any problems (https://dnsimple.statuspage.io/) and all the checks I can run come back without a problem:

dig infosec.exchange @ns1.dnsimple-edge.net

; <<>> DiG 9.18.39-0ubuntu0.22.04.3-Ubuntu <<>> infosec.exchange @ns1.dnsimple-edge.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15656
;; flags: qr aa rd; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;infosec.exchange. IN A

;; ANSWER SECTION:
infosec.exchange. 3600 IN A 151.101.3.52
infosec.exchange. 3600 IN A 151.101.67.52
infosec.exchange. 3600 IN A 151.101.131.52
infosec.exchange. 3600 IN A 151.101.195.52

;; Query time: 12 msec
;; SERVER: 2620:111:8004::53#53(ns1.dnsimple-edge.net) (UDP)
;; WHEN: Tue May 12 14:42:29 UTC 2026
;; MSG SIZE rcvd: 109

]]>https://board.circlewithadot.net/post/https://infosec.exchange/users/jerry/statuses/116562138338380943https://board.circlewithadot.net/post/https://infosec.exchange/users/jerry/statuses/116562138338380943Tue, 12 May 2026 14:44:41 GMT