Google’s 8.8.8.8 resolves ok while 1.1.1.1 and 1.0.0.1 do not.
I had to switch to 8.8.8.8 since it keeps not resolving.
dig +short CHAOS TXT id.server @1.0.0.1 or @1.1.1.1 reports PRG
$ dig @1.1.1.1 subtchallenge.com
; <<>> DiG 9.11.3-1ubuntu1.13-Ubuntu <<>> @1.1.1.1 subtchallenge.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 50503
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; OPT=15: 00 06 ("..")
;; QUESTION SECTION:
;subtchallenge.com. IN A
;; Query time: 784 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Mon Oct 26 13:22:05 CET 2020
;; MSG SIZE rcvd: 52
$ dig @1.0.0.1 subtchallenge.com
; <<>> DiG 9.11.3-1ubuntu1.13-Ubuntu <<>> @1.0.0.1 subtchallenge.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 5242
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; OPT=15: 00 06 ("..")
;; QUESTION SECTION:
;subtchallenge.com. IN A
;; Query time: 681 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Mon Oct 26 13:22:41 CET 2020
;; MSG SIZE rcvd: 52
$ dig @8.8.8.8 subtchallenge.com ; <<>> DiG 9.11.3-1ubuntu1.13-Ubuntu <<>> @8.8.8.8 subtchallenge.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9876 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;subtchallenge.com. IN A ;; ANSWER SECTION: subtchallenge.com. 21599 IN A 192.5.18.235 ;; Query time: 317 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Mon Oct 26 13:23:05 CET 2020 ;; MSG SIZE rcvd: 62
$ dig @8.8.4.4 subtchallenge.com ; <<>> DiG 9.11.3-1ubuntu1.13-Ubuntu <<>> @8.8.4.4 subtchallenge.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27784 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;subtchallenge.com. IN A ;; ANSWER SECTION: subtchallenge.com. 21575 IN A 192.5.18.235 ;; Query time: 23 msec ;; SERVER: 8.8.4.4#53(8.8.4.4) ;; WHEN: Mon Oct 26 13:23:29 CET 2020 ;; MSG SIZE rcvd: 62
$ dig @ns3.Cloudflare.com whoami.Cloudflare.com 123 txt +shortreports nothing (no output).
The problem persists. Should I supply some other information in order to help debugging?
Hi @zbynek.winkler,
Thanks for the report, I can reproduce. It seems an issue between our colo and upstream auth servers. We’ll try to figure it out.
It is resolving now.
@anb It seems that community.subtchallenge.com subdomain exhibits the same problem as its parent domain used to exhibit:
$ dig @1.1.1.1 community.subtchallenge.com
; <<>> DiG 9.11.3-1ubuntu1.13-Ubuntu <<>> @1.1.1.1 community.subtchallenge.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 65495
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; OPT=15: 00 06 ("..")
;; QUESTION SECTION:
;community.subtchallenge.com. IN A
;; Query time: 1031 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Thu Dec 17 08:38:59 CET 2020
;; MSG SIZE rcvd: 62
while
$ dig @8.8.8.8 community.subtchallenge.com ; <<>> DiG 9.11.3-1ubuntu1.13-Ubuntu <<>> @8.8.8.8 community.subtchallenge.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39230 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;community.subtchallenge.com. IN A ;; ANSWER SECTION: community.subtchallenge.com. 21599 IN A 192.5.18.235 ;; Query time: 645 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Thu Dec 17 08:38:51 CET 2020 ;; MSG SIZE rcvd: 72
Hi, sorry about that. I added another workaround. It should be working now.