Changing CloudFlare DNS records

Hi everyone!

I changed my hosting package, so I made some changes on CloudFlare DNS records to point to the new hosting server. It was more than 1 hour ago, and now it still doesn’t work.

Anybody know usually how long does it take for CloudFlare to work with new DNS records.

Thanks.

Hi @toanphung.vn,

If the records are :orange: then it should be almost instantaneous, a couple of minutes at most. If they are :grey:, it can take quite a while…

Thanks for your prompt reply. However I don’t know what you mean. In DNS tab, we can click to the grey cloud to make it orange cloud. Is that right?

:grey: means you are only using Cloudflare for DNS, while :orange: means you are using Cloudflare’s services, performance, security, SSL etc.

If you are using DNS only, the DNS records could take a while (probably about 24hrs) to fully propagate.

Thanks for your reply.

I use orange ones. More than 1 hour, but it still doesn’t work.

Could you please help by taking a look at the DNS records below (my hosting is DreamPress).

A cat points to 66.33.203.11
A cruiseshalongbay.com points to 69.163.149.178
A db points to 66.33.203.11
A ftp points to 69.163.149.178
A mysql points to 66.33.203.11
A mysql534 points to 69.163.149.178
A ssh points to 69.163.149.178
A www points to 69.163.149.178

Thanks a lot.

Thanks for your reply.

I use orange ones. More than 1 hour, but it still doesn’t work.

Could you please help by taking a look at the DNS records below (my hosting is DreamPress).

A cat points to 66.33.203.11
A cruiseshalongbay.com points to 69.163.149.178
A db points to 66.33.203.11
A ftp points to 69.163.149.178
A mysql points to 66.33.203.11
A mysql534 points to 69.163.149.178
A ssh points to 69.163.149.178
A www points to 69.163.149.178
CNAME calendar is an alias of ghs.googlehosted.com
CNAME docs is an alias of ghs.googlehosted.com
CNAME mail is an alias of ghs.googlehosted.com
CNAME sites is an alias of ghs.googlehosted.com
CNAME start is an alias of ghs.googlehosted.com
MX cruiseshalongbay.com mail handled by aspmx.l.google.com
TXT cruiseshalongbay.com v=spf1 include:_spf.google.com ~all

Thanks a lot.

In this case it shouldnt be a DNS issue.

Your site actually loads fine -> http://sitemeer.com/#https://www.cruiseshalongbay.com/. Can you post the output of these four commands?

ping cruiseshalongbay.com
ping www.cruiseshalongbay.com
nslookup cruiseshalongbay.com
nslookup www.cruiseshalongbay.com

Yes, it works fine now. It was SSL problem.
Thanks all.

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