I've heard back from many of you and directly from Quad9 that they are removing the block on infosec.exchange, but it'll take some time for that to flush through their system. The internet is, after all, a series of sewer pipes.
Still not showing as unblocked by quad9. The sewers must be really backed up today. Guessing there is a problem with all that swamp water.
I feel like I need to clarify: quad9 is not a sewer. The internet itself is the sewer. Quad9 is trying to run a wastewater treatment facility, which is not a terrible thing.
@jerry As moderator, you're the sewage truck operator that pumps out septic tanks. Thanks for your service! 🫑
@jawnsy this one hits home. I do smell the sewage smell coming from those moderation reports
@jerry when you said sewer, for some unknown reason my brain immediately went to X, Facebook, and Instagram
@jerry One can think of it as a place where all the fatbergs pile up...
ok - it's showing unblocked in all of my global queries now.
@jerry Still taking a while...not seeing it here in Northern Virginia.
@darthnull probably because there’s no internet infrastructure in that part of the country πŸ˜‚
@jerry ha! And the second after I posted that, I tried again, and it worked. Literally 40 seconds after it'd failed.

@jerry Works here:

; <<>> DiG 9.18.29 <<>> a infosec.exchange @9.9.9.9
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30251
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

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

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

;; Query time: 31 msec
;; SERVER: 9.9.9.9#53(9.9.9.9) (UDP)
;; WHEN: Thu Feb 06 17:23:39 CET 2025
;; MSG SIZE rcvd: 109

@jerry

Is there a Router Rooter franchise we can call?