DNS CNAME record not propagating

Hey guys,
I had a A record training.rockcontent.com pointing to an ip using the CloudFlare proxy.

5 days ago, i had to delete it and add a CNAME to an AWS S3 Bucket address training.rockcontent.com.s3-website-us-east-1.amazonaws.com, it isn’t using the CF proxy.

Since then, the new site is not working, surprisingly the old site is, and when i verify the DNS entry, it shows an CloudFront ip.

CloudFlare Configuration:

Verify DNS using 1.1.1.1 as resolver.

Hi @andre.chagas,

Can you check that the nameservers shown below your DNS records are eva and rick, just to make sure that’s the active account.

If they do match, what service did that subdomain previously use? If it could have been a Cloudflare Custom Hostnames / SSL for SaaS customer, you may need to contact them to release your domain from their Cloudflare configuration.

1 Like

Though I’d expect it it’s DNS Only, that type of integration wouldn’t affect unless it’s :orange: Proxied.

1 Like

The nameservers are configured OK, i already created a new record and it worked, only this record is not working.
I`m only using the DNS record, not the proxy, so at least the response on the subdomain query should change to the new value, but it isn’t working.

─ dig ns rockcontent.com

; <<>> DiG 9.10.6 <<>> ns rockcontent.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40852
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;rockcontent.com. IN NS

;; ANSWER SECTION:
rockcontent.com. 86400 IN NS eva.ns.cloudflare.com.
rockcontent.com. 86400 IN NS rick.ns.cloudflare.com.

;; Query time: 35 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Thu Jul 29 12:30:58 -03 2021
;; MSG SIZE rcvd: 95

##################################

─ dig ns @8.8.8.8 rockcontent.com

; <<>> DiG 9.10.6 <<>> ns @8.8.8.8 rockcontent.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58472
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;rockcontent.com. IN NS

;; ANSWER SECTION:
rockcontent.com. 84709 IN NS eva.ns.cloudflare.com.
rockcontent.com. 84709 IN NS rick.ns.cloudflare.com.

;; Query time: 54 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Jul 29 12:31:39 -03 2021
;; MSG SIZE rcvd: 95

#####################################

dig ns @1.1.1.1 rockcontent.com

; <<>> DiG 9.10.6 <<>> ns @1.1.1.1 rockcontent.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22941
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;rockcontent.com. IN NS

;; ANSWER SECTION:
rockcontent.com. 80422 IN NS eva.ns.cloudflare.com.
rockcontent.com. 80422 IN NS rick.ns.cloudflare.com.

;; Query time: 41 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Thu Jul 29 12:32:25 -03 2021
;; MSG SIZE rcvd: 95

He meant at the bottom of your DNS settings page at dash.cloudflare.com (the two Cloudflare name servers should be listed there)

Yes, it is using :ngrey: (without proxy).


Yes it is using the rick and eva.

It wouldn’t be the first time a DNS record got stuck. Support can “rebuild” the zone, and that should fix it.

Open a ticket and ask them if they can rebuild your zone due to the stuck DNS record. Make sure you post the ticket # here. Contact them at support AT cloudflare DOT com

1 Like

Thanks a lot, i will try it now, and post here if it works!

1 Like

Here is the ticket
https://support.cloudflare.com/hc/requests/2218351

1 Like

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