Cnbeta.com can't be resolved


#1

cnbeta.com cant be succesfully resolved by 1.1.1.1 sometimes. If I change to 8.8.8.8, no issue immediately.

It’s weird that it shows no error by using dig.

; <<>> DiG 9.10.6 <<>> cnbeta.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40147
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
cnbeta.com. 2706 IN A 125.90.93.20

;; Query time: 35 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Wed Apr 18 14:58:24 +08 2018
;; MSG SIZE rcvd: 55

BindeMac-mini:~ liciece$ dig cnbeta.com @8.8.8.8

; <<>> DiG 9.10.6 <<>> cnbeta.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30639
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
cnbeta.com. 3599 IN A 125.90.93.20

;; Query time: 97 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Apr 18 15:00:11 +08 2018
;; MSG SIZE rcvd: 55


#3

Yesterday I saw this once with did, but today it seems to be resolving consistently. I’ve passed along a note to the resolver team but I don’t have a definitive cause here for the issue that jumps out at me.


#4

Sure. Thanks.


#5

I can’t say their authoritative servers are in a perfect state, so I guess that’s closely related: http://dnsviz.net/d/www.cnbeta.com/WtSfuw/dnssec/


#6

I think this might be the reason why it couldn’t be resolved sometimes.


#7

This topic was automatically closed after 14 days. New replies are no longer allowed.