DNS NXDOMAIN errors

Website, Application, Performance DNS & Network
1

We noticed that you applied a fix yesterday, but today our clients still receive that errors.

Cloudflare system status

17:00 21-06-2021

Authoritative DNS lookup problems for some Free plan zones

  • A fix has been implemented and we are monitoring the results. [27 minutes ago]
  • A small number of free zones are seeing NXDOMAIN responses [2 hours ago]

Are you monitoring the problem?

Thank you!

2

Can you give some examples of what you are seeing please? Output from a failing location with these commands is useful:

dig example.com
dig example.com @1.1.1.1
dig example.com @8.8.8.8
curl example.com/cdn-cgi/trace
traceroute simon.ns.cloudflare.com

Replace example.com with the hostname you are seeing issues with.

3

Hello,

I run the commands and all seems correct. I hidden some data, because this is a public forum.
The NXDOMAIN errors continue:

errors_NXDOMAIN
errors_NXDOMAIN975×473 24.9 KB 

dig www.example.com
; <<>> DiG 9.10.3-P4-Ubuntu <<>> www.example.es
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58732
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.example.es.              IN      A

;; ANSWER SECTION:
www.example.es.       300     IN      A       * hidden *

;; Query time: 39 msec
;; SERVER: 10.0.0.2#53(10.0.0.2)
;; WHEN: Wed Jun 30 11:17:39 UTC 2021
;; MSG SIZE  rcvd: 61

dig www.example.com @1.1.1.1
; <<>> DiG 9.10.3-P4-Ubuntu <<>> www.example.es @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59480
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;www.example.es.              IN      A

;; ANSWER SECTION:
www.example.es.       300     IN      A       * hidden *

;; Query time: 57 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Wed Jun 30 11:17:39 UTC 2021
;; MSG SIZE  rcvd: 61

dig www.example.com @8.8.8.8
; <<>> DiG 9.10.3-P4-Ubuntu <<>> www.example.es @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3532
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.example.es.              IN      A

;; ANSWER SECTION:
www.example.es.       299     IN      A       * hidden *

;; Query time: 25 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Jun 30 11:17:39 UTC 2021
;; MSG SIZE  rcvd: 61

curl www.example.com/cdn-cgi/trace
[Webpage content]

traceroute simon.ns.cloudflare.com
traceroute to simon.ns.cloudflare.com (108.162.193.232), 30 hops max, 60 byte packets
 1  * hidden *
 2  * hidden *
 3  100.66.11.136 (100.66.11.136)  16.838 ms 100.66.25.74 (100.66.25.74)  7.939 ms 100.66.10.106 (100.66.10.106)  15.846 ms
 4  100.66.7.203 (100.66.7.203)  16.516 ms 100.66.7.135 (100.66.7.135)  14.126 ms 100.66.11.96 (100.66.11.96)  17.646 ms
 5  100.66.6.143 (100.66.6.143)  487.756 ms 100.66.5.211 (100.66.5.211)  21.083 ms 100.66.5.179 (100.66.5.179)  110.729 ms
 6  100.65.15.143 (100.65.15.143)  8.365 ms 100.66.5.253 (100.66.5.253)  15.699 ms 100.65.14.5 (100.65.14.5)  0.390 ms
 7  100.65.13.11 (100.65.13.11)  0.318 ms 100.65.15.133 (100.65.15.133)  0.837 ms 100.65.13.17 (100.65.13.17)  0.560 ms
 8  100.100.16.96 (100.100.16.96)  1.216 ms 100.95.19.157 (100.95.19.157)  11.275 ms 100.95.19.145 (100.95.19.145)  0.304 ms
 9  100.100.16.94 (100.100.16.94)  1.452 ms inex1.as13335.net (185.6.36.76)  24.782 ms 100.100.16.122 (100.100.16.122)  1.025 ms
10  inex1.as13335.net (185.6.36.76)  23.580 ms 100.100.2.6 (100.100.2.6)  0.814 ms inex1.as13335.net (185.6.36.76)  22.688 ms
11  simon.ns.cloudflare.com (108.162.193.232)  0.736 ms  0.735 ms  0.710 ms
4

Are you having reports from clients and users of real issues?

Some level of NXDOMAIN is expected - somewhat like HTTP 404 (Page Not Found) errors - if someone mistypes or you have an old link somewhere, you will get these.

5

Of course, our clients are reporting that they are using the webpage normally, and then the NXDOMAIN error appears like there is no webpage with that domain (https://www.wpbeginner.com/wp-content/uploads/2020/11/nxdomain-error-example-chrome.png).

6

OK - in the command outputs you have so far everything looks good - no NXDOMAIN can be replicated. have you been able to have someone run those commands when the failure happens?

7

Is difficult to request that to the clients as you can understand, they don’t even know how to open the CMD :s
For now, if you don’t have an opened incidence of NXDOMAIN errors right know, we can not give you more information.
If we could get that info I’ll write here again.
Thank you!

8

We don’t have any ongoing issues impacting other customers relating to NXDOMAIN - if you have a specific DNS record you’re seeing an issue with - I can raise a Support ticket in your account to check specifics.

9

I could give you the DNS record if you give me some option to do it privately.
Thank you!

10

I have raised a ticket in your account for you so we can share information there.

11

Thank you Simon for all your support, talk to you there :slight_smile:

12

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.