Diytrade.com can't lookup on 1.1.1.1

What is status 2 stand for ?

curl -v “https://1.1.1.1/dns-query?ct=application/dns-json&name=diytrade.com

{“Status”: 2,“TC”: false,“RD”: true, “RA”: true, “AD”: false,“CD”: false,“Question”:[{“name”: “diytrade.com.”, “type”: 1}]}

dig +short CHAOS TXT id.server @1.1.1.1
“NRT”

dig diytrade.com @1.1.1.1

; <<>> DiG 9.11.3-1ubuntu1.7-Ubuntu <<>> diytrade.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 38351
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;diytrade.com. IN A

;; Query time: 1 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Tue Jun 18 10:55:20 JST 2019
;; MSG SIZE rcvd: 41

dig diytrade.com @8.8.8.8

; <<>> DiG 9.11.3-1ubuntu1.7-Ubuntu <<>> diytrade.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31391
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
diytrade.com. 10799 IN A 121.201.119.7

;; Query time: 52 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Jun 18 10:55:35 JST 2019
;; MSG SIZE rcvd: 57

At first glance things look okay, at least in that I get similar results from various public and private resolvers. However, ns4.diyworld.com is not responding, and I got timeouts from ns5.diyworld.com at least a couple times although it does respond now, so perhaps there are some intermittent issues at diyworld.com?

So strange ! I don’t have problem on query those servers in China, Japan and USA !

Why there is no problem on google and quad9 ?

dig diyworld.com @8.8.8.8

; <<>> DiG 9.11.3-1ubuntu1.7-Ubuntu <<>> diyworld.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44768
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
diyworld.com. 21599 IN A 218.213.70.169

;; Query time: 54 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Jun 18 16:03:11 JST 2019
;; MSG SIZE rcvd: 57

dig diyworld.com @9.9.9.9

; <<>> DiG 9.11.3-1ubuntu1.7-Ubuntu <<>> diyworld.com @9.9.9.9
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1875
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
diyworld.com. 43200 IN A 218.213.70.169

;; Query time: 478 msec
;; SERVER: 9.9.9.9#53(9.9.9.9)
;; WHEN: Tue Jun 18 16:03:18 JST 2019
;; MSG SIZE rcvd: 57

dig diyworld.com @1.1.1.1

; <<>> DiG 9.11.3-1ubuntu1.7-Ubuntu <<>> diyworld.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 48544
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;diyworld.com. IN A

;; Query time: 1 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Tue Jun 18 16:03:23 JST 2019
;; MSG SIZE rcvd: 41

Seem some problem from our ns4 to 1.1.1.1

dig +short +tcp 853 A whoami.akamai.net @1.1.1.1

;; Connection to 1.1.1.1#53(1.1.1.1) for whoami.akamai.net failed: connection refused.

dig +short +tcp 853 A whoami.akamai.net @1.0.0.1

162.158.57.244

dig +short +tcp 853 A whoami.akamai.net @1.1.1.1

;; Connection to 1.1.1.1#53(1.1.1.1) for whoami.akamai.net failed: connection refused.

traceroute 1.1.1.1

traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
1 10.120.1.12 (10.120.1.12) 0.293 ms 0.210 ms 0.205 ms
2 * * *
3 114.118.0.233 (114.118.0.233) 29.131 ms 114.118.0.237 (114.118.0.237) 4.952 ms 114.118.0.233 (114.118.0.233) 29.546 ms

Ns4 is in China ! Is it the problem ? Also the same problem is occurring in Ns2.diyworld.com

dig +short CHAOS TXT id.server @1.1.1.1

“LAX”

dig +short CHAOS TXT id.server @1.0.0.1

“SJC”

What is the reason for only Cloudflare can’t resolve the domain ?

1 Like

We have asked the provider to fix the route. and how about the ns3.diyworld.com ?

Why ?