More than 72 hours after replacing nameservers from the default ones from namecheap to cloudflare, the domain is still not resolved in many locations on the planet, including 1.0.0.1.
What can be wrong?
dig NS rocketly.app @1.0.0.1
; <<>> DiG 9.10.6 <<>> NS rocketly.app @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 13802
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; OPT=15: 00 09 6e 6f 20 53 45 50 20 6d 61 74 63 68 69 6e 67 20 74 68 65 20 44 53 20 66 6f 75 6e 64 20 66 6f 72 20 72 6f 63 6b 65 74 6c 79 2e 61 70 70 2e ("..no SEP matching the DS found for rocketly.app.")
;; QUESTION SECTION:
;rocketly.app. IN NS
;; Query time: 46 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Mon Mar 25 09:38:53 MSK 2024
;; MSG SIZE rcvd: 93
Your DNSSEC configuration is broken. You should shut it off at Cloudflare, or take the Cloudflare-generated DS records and add them at your registrar.
You’ll find these things in the DNS section in the Cloudflare dashboard (magic link).
2 Likes
Yeah, you are right, thanks.
For everyone who meets the same problem, pay attention to this:
I’ve enabled DNSSEC and added a record on Namecheap.
2 Likes
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.