DNS TXT change stuck in pending for _amazonses entry

Question

When I originally entered a TXT record set for _amazonses I had copied and pasted the value with an extra space via route53.    
  
"p0PMfJ_.../In_00G6MtY=" was mistakenly set at "p0PMfJ_.../In_00G6MtY= ".  
  
I have since corrected it to strip the whitespace several days ago and had been waiting for it to propagate, but it didn't.  I checked by running this at my command prompt:  
  
dig TXT _amazonses..com  
  
Indeed the trailing space remained from the output of that command.  
  
I then attempted to force restart the process by deleting the record set and creating a new one. The trailing space remains and the verification status of this record is still pending.  
  
Is there possibly something that matches the original value for the TXT recordset and, if it is ignoring the whitespace, does not submit this record set to be propagated?

Answer

**Update**  
  
Scott was able to see that I had two accounts with two different hosted zones using the same domain name.  One hosted zone was setup in Amazon lightsail and the other was setup in route53.  The lightsail hosted zone was the one registered with the domain servers.  I had been trying to fix the other. I had not realized you wouldn't be able to see the lightsail hosted zones in route53 so had manually added them there mistakenly.  
  
With Scott's direction, I deleted the hosted zone in route53 and am managing the _amasonses TXT recordset with lightsail.  Now everything works like a charm!  
  
Thank for the assist Scott!

Answer

Hi,  
  
If you post your domain name, I'll take a look at your configuration.  
  
Scott

DNS TXT change stuck in pending for _amazonses entry

Relevant content