DNS records not resolving after 1 day

[user9094]

About 24 hours ago, I changed the NS servers for dramarianelagilardi.com to Cloudflare. However, I can’t get any of the CNAMEs to resolve.

This happened already earlier in the week, and using Amazon Route53 worked instantly. Now I want to try and fix things here at Cloudflare.

I also tried deleting the website, and creating it again.

NS all good:

dig @1.1.1.1 ns dramarianelagilardi.com
;; ANSWER SECTION:
dramarianelagilardi.com. 86400	IN	NS	heather.ns.cloudflare.com.
dramarianelagilardi.com. 86400	IN	NS	todd.ns.cloudflare.com.

CNAMEs in dash:

No CNAMEs resolving:

dig @1.1.1.1 cname www.dramarianelagilardi.com
; <<>> DiG 9.10.6 <<>> @1.1.1.1 cname www.dramarianelagilardi.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 60828
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;www.dramarianelagilardi.com.	IN	CNAME

;; AUTHORITY SECTION:
dramarianelagilardi.com. 3600	IN	SOA	heather.ns.cloudflare.com. dns.cloudflare.com. 1675612474 10000 2400 604800 3600

;; Query time: 138 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Sun Feb 05 10:54:33 EST 2023
;; MSG SIZE  rcvd: 118

dig @1.1.1.1 cname www2.dramarianelagilardi.com

; <<>> DiG 9.10.6 <<>> @1.1.1.1 cname www2.dramarianelagilardi.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 49995
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;www2.dramarianelagilardi.com.	IN	CNAME

;; AUTHORITY SECTION:
dramarianelagilardi.com. 3600	IN	SOA	heather.ns.cloudflare.com. dns.cloudflare.com. 1675612507 10000 2400 604800 3600

;; Query time: 210 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Sun Feb 05 10:55:07 EST 2023
;; MSG SIZE  rcvd: 119

dig @1.1.1.1 cname www3.dramarianelagilardi.com

; <<>> DiG 9.10.6 <<>> @1.1.1.1 cname www3.dramarianelagilardi.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54792
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;www3.dramarianelagilardi.com.	IN	CNAME

;; AUTHORITY SECTION:
dramarianelagilardi.com. 3600	IN	SOA	heather.ns.cloudflare.com. dns.cloudflare.com. 1675612519 10000 2400 604800 3600

;; Query time: 12 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Sun Feb 05 10:55:19 EST 2023
;; MSG SIZE  rcvd: 119

Same checking online:

• https://www.whatsmydns.net/#CNAME/www.dramarianelagilardi.com
• https://www.whatsmydns.net/#CNAME/www2.dramarianelagilardi.com
• https://www.whatsmydns.net/#CNAME/www3.dramarianelagilardi.com

[cbrandt]

Do you have an A record for the naked domain? If not, I think you need to create one pointing to an IP address and proxy it so that the CNAMEs start to respond.

Source:

DNS record types · Cloudflare DNS docs

[epic.network]

The www, www2 & www3 CNAMEs all point to an external domain, not the apex, so that should not matter. Based on the DNS dashboard configuration as shown, we should expect to see CNAMEs returned for www & www2. The www3 hostname should not return a CNAME since it is proxied. We should see synthetic A & AAAA records with Cloudflare proxy IPs.

The DNSSEC looks fine. It is is definitely a curious situation you have shared here.

[simon]

We’ll look at this internally and get back to you here - it’s not clear exactly why this is happening.

[bernardo.reino]

FWIW it seems OK now, i.e. the CNAME resolves just fine.

[simon]

Yes - our DNS team just found an issue with this domain internally and fixed it for you. Thanks for raising this.