CNAME record not propagating after 24 hours

I set up a CNAME record 24 hours ago and it still is not propagating. It seems to be done correctly in my CF DNS settings. All of the other CNAMES are working as expected. It is supposed to be client-portal.syncresis.com aliasing to custom-domains.clinked.com. clinked.com is supposed to be serving a white-label version of their web application. The link works but it fails to display. Their response is that the CNAME record is not there, which external DNS checkers confirms is the case: DNS Checker - DNS Check Propagation Tool and DNS Propagation Checker - Global DNS Testing Tool both show no record existing.

What could be causing this?

I don’t see any issues on my side, the website works fine.

Er as I am typing this the DNS records changed. Do you still require help?

$ kdig client-portal.syncresis.com
;; ->>HEADER<<- opcode: QUERY; status: NOERROR; id: 31344
;; Flags: qr rd ra; QUERY: 1; ANSWER: 3; AUTHORITY: 0; ADDITIONAL: 0

;; QUESTION SECTION:
;; client-portal.syncresis.com.		IN	A

;; ANSWER SECTION:
client-portal.syncresis.com.	377	IN	CNAME	custom-domains.clinked.com.
custom-domains.clinked.com.	77	IN	A	54.171.46.41
custom-domains.clinked.com.	77	IN	A	52.213.16.53

;; Received 114 B
;; Time 2019-01-16 09:56:41 AEDT
;; From 172.20.10.1@53(UDP) in 569.8 ms

 $ kdig client-portal.syncresis.com
;; ->>HEADER<<- opcode: QUERY; status: NOERROR; id: 2337
;; Flags: qr rd ra; QUERY: 1; ANSWER: 2; AUTHORITY: 0; ADDITIONAL: 0

;; QUESTION SECTION:
;; client-portal.syncresis.com.		IN	A

;; ANSWER SECTION:
client-portal.syncresis.com.	116	IN	A	104.25.168.116
client-portal.syncresis.com.	116	IN	A	104.25.167.116

;; Received 77 B
;; Time 2019-01-16 10:30:02 AEDT
;; From 172.20.10.1@53(UDP) in 13.7 ms

Thank you for that. It’s still not being detected as a CNAME on most DNS checkers but I think that may be by design because Cloudflare only returns IP addresses. It may be a problem with Clinked rather than CF. I’m going to share the data with them.

1 Like

Cloudflare does support the CNAME record (:grey:) but If the root (apex) domain has a CNAME record Cloudflare flattens the domain.
https://support.cloudflare.com/hc/en-us/articles/200169056-CNAME-Flattening-RFC-compliant-support-for-CNAME-at-the-root

Also if the requests are proxied via Cloudflare (:orange:) CNAMEs are replaced with A records

1 Like

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