Domain cannot be resolved with CloudFlare resolver

Zero Trust 1.1.1.1
1

Hello, many users complaint they cannot resolve our site, and that occurs when they are using 1.0.0.1/1.1.1.1

Both domains are hosted in AWS route53, review the settings and seem fine:

nslookup demo.marketplace.pairity.io 1.1.1.1
Server: 1.1.1.1
Address: 1.1.1.1#53

** server can’t find demo.marketplace.pairity.io: NXDOMAIN

nslookup staging.marketplace.pairity.io 1.1.1.1
Server: 1.1.1.1
Address: 1.1.1.1#53

** server can’t find staging.marketplace.pairity.io: NXDOMAIN

Same applies to 1.0.0.1

dig demo.marketplace.pairity.io @1.1.1.1

; <<>> DiG 9.10.6 <<>> demo.marketplace.pairity.io @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 43847
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;demo.marketplace.pairity.io. IN A

;; AUTHORITY SECTION:
marketplace.pairity.io. 692 IN SOA ns-1699.awsdns-20.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400

;; Query time: 40 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Wed Aug 12 18:25:31 -03 2020
;; MSG SIZE rcvd: 165

dig staging.marketplace.pairity.io @1.1.1.1

; <<>> DiG 9.10.6 <<>> staging.marketplace.pairity.io @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 60849
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;staging.marketplace.pairity.io. IN A

;; AUTHORITY SECTION:
marketplace.pairity.io. 82 IN SOA ns-1699.awsdns-20.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400

;; Query time: 39 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Wed Aug 12 18:26:40 -03 2020
;; MSG SIZE rcvd: 168

Any idea what could be wrong? Thanks!

2

They’re not so great at 8.8.8.8 and 9.9.9.9 either.

Screen Shot 2020-08-12 at 2.29.58 PM
Screen Shot 2020-08-12 at 2.29.58 PM1106×510 133 KB

3

@sdayman at least it works for me and we have not received complains about it on other DNS provider:

image
image1316×458 37.6 KB

4

It doesn’t always work because NS for marketplace.pairity.io is returning NXDOMAIN to its subdomain.
Make sure you have a correct NS for ‘staging’ inside the marketplace.pairity.io zone.

$ kdig @a2.nic.io pairity.io
..
pairity.io.         	86400	IN	NS	ns-1647.awsdns-13.co.uk.
pairity.io.         	86400	IN	NS	ns-1523.awsdns-62.org.
pairity.io.         	86400	IN	NS	ns-840.awsdns-41.net.
pairity.io.         	86400	IN	NS	ns-379.awsdns-47.com.

$ kdig @ns-1647.awsdns-13.co.uk marketplace.pairity.io
..
marketplace.pairity.io.	60	IN	NS	ns-1046.awsdns-02.org.
marketplace.pairity.io.	60	IN	NS	ns-1699.awsdns-20.co.uk.
marketplace.pairity.io.	60	IN	NS	ns-612.awsdns-12.net.
marketplace.pairity.io.	60	IN	NS	ns-88.awsdns-11.com.

$ kdig @ns-1046.awsdns-02.org staging.marketplace.pairity.io
;; ->>HEADER<<- opcode: QUERY; status: NXDOMAIN; id: 8169
;; Flags: qr aa rd; QUERY: 1; ANSWER: 0; AUTHORITY: 1; ADDITIONAL: 0

;; QUESTION SECTION:
;; staging.marketplace.pairity.io.		IN	A

;; AUTHORITY SECTION:
marketplace.pairity.io.	900	IN	SOA	ns-1699.awsdns-20.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400