cant validate ms txt

Question

Hello, I added the TXT record as requested for Microsoft 365 verification.
- Hosted zone: akcoreconsulting.com
- Record name: @
- Record type: TXT
- Value: "MS=5E712817E430205B193FCFD3DEA0E581F9FB7550"
But external tools (e.g., MXToolbox) do not show the record, and the SOA serial stays at 1 no matter what changes are made in the zone.
How can I get Route 53 to increment the SOA serial or propagate this record externally?
Thanks!

Riku_Kobayashi · Accepted Answer

Hello.

Route53 does not require you to enter the "@" sign when creating an APEX record.  
Therefore, if you want to create a TXT record for the domain "akcoreconsulting.com", you should leave the Record name field blank.  
![a](/media/postImages/original/IM935VkZg9RBaz-KmNZik_Rw)

re:Post Agent · Answer

It sounds like you're experiencing issues with your TXT record not propagating correctly in Route 53. This can be frustrating, but there are a few things we can check to help resolve the issue:

1. DNS Propagation Time: DNS changes can take up to 48-72 hours to fully propagate across the internet. If you've recently added the TXT record, it might not be immediately visible to external tools. Wait for at least 24-48 hours before trying to verify again.

2. Record Format: Ensure that the TXT record is formatted correctly. Some DNS providers require that you enter the value without quotation marks, while others may require them. Double-check the exact format required by Microsoft 365.

3. Name Servers: Verify that your domain is using the correct Route 53 name servers. In the Route 53 console, under "Registered Domains," select your domain and check the name servers listed under "Details." Make sure these match the name servers in your hosted zone.

4. SOA Serial: Route 53 manages the SOA serial automatically, and it doesn't necessarily increment with every change. This behavior is normal and shouldn't affect the propagation of your records.

5. Record Visibility: Use the `dig` command or other DNS lookup tools to check if the TXT record is visible from different locations. Sometimes, caching or specific DNS servers might not show the updated records immediately.

6. Multiple TXT Records: If there are multiple TXT records for the same domain, ensure the Microsoft 365 TXT record is not being overshadowed by others.

If you've checked all these points and are still having issues, you may want to contact AWS support for further assistance. They can help investigate if there are any specific issues with your hosted zone or record propagation.

Remember, patience is key when dealing with DNS changes. If everything looks correct on your end, giving it more time to propagate might be the solution.
      
**Sources**  
[I transferred the domain to Route 53 and created a DNS zone, but unable to verify using txt record. | AWS re:Post](https://repost.aws/questions/QUTRi8iQtSRzem2nJiDBzleg/i-transferred-the-domain-to-route-53-and-created-a-dns-zone-but-unable-to-verify-using-txt-record)  
[TXT record not verifying with Klaviyo (third party) integration | AWS re:Post](https://repost.aws/questions/QUEtI_PYURRVakzFH9PjmiXA/txt-record-not-verifying-with-klaviyo-third-party-integration)  
[Lightsail DNS Record Not Verified | AWS re:Post](https://repost.aws/questions/QUT5hNyay-SmyAGW8peEMdWw/lightsail-dns-record-not-verified)

cant validate ms txt

Relevant content