Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

TXT records not propagation

Former Community Member
Not applicable

I've added 2 new TXT records that are needed for Cloudways. I waited over 72 hours. They never propagated. I removed the records and tried again...with the same results. I have one working TXT record which I made when I initially setup the domain. As a test, I modified it, and it propagated almost immediately. Any ideas why my new TXT records are not propagating?

Solved Solved
0 2 2,037
1 ACCEPTED SOLUTION

Former Community Member
Not applicable

I did find a solution...but first to answer you questions.

1. no errors. The 2 TXT records just never propagated. (over a week waiting)
2. all the other records continued to work fine
3. none needed

I've done this a lot in the past, so I'm fairly experienced. Prior to using Google CloudDNS, I was on AWS Route 53 for over a decade. To be honest, I've never had a similar experience.

And now for the solution: I moved the DNS to CloudFlare's DNS services...and it worked first time - like a charm. This leads me to believe it is a bug in Google's CloudDNS.

 

View solution in original post

2 REPLIES 2

Hi @Former Community Member ,

To better answer your question, it would be very helpful if you will add details to it. Can you share the following:

1. Error message obtained when you mentioned "I removed the records and tried again...with the same results."
2. Was this working fine before before you added the 2 new TXT records?
3. Were you following any documentations or guides when you set it up?

Former Community Member
Not applicable

I did find a solution...but first to answer you questions.

1. no errors. The 2 TXT records just never propagated. (over a week waiting)
2. all the other records continued to work fine
3. none needed

I've done this a lot in the past, so I'm fairly experienced. Prior to using Google CloudDNS, I was on AWS Route 53 for over a decade. To be honest, I've never had a similar experience.

And now for the solution: I moved the DNS to CloudFlare's DNS services...and it worked first time - like a charm. This leads me to believe it is a bug in Google's CloudDNS.