Why there is DNS Propagation Delays For Route 53 Hosted website

DNS propagation delays can occur for several reasons when you're changing DNS settings for a domain in Route 53. In your case with Shopify integration, there are a few potential causes and solutions:

1. Name server propagation: When you change the name servers for a domain, it can take up to 48 hours for the change to fully propagate across all DNS resolvers worldwide. DNS resolvers typically request name server information only once every two days and cache the answer.

2. TTL values: Check the Time-to-Live (TTL) values on your DNS records. If they're set too high, DNS resolvers will cache the old information longer. Consider lowering your TTL values to 60 seconds or less for faster propagation during changes.

3. Inconsistent record configuration: Verify that all required records (A, AAAA, CNAME) are correctly configured according to Shopify's requirements. Any missing or incorrect records can lead to inconsistent DNS resolution.

4. Multiple hosted zones: Ensure you're not updating records in the wrong hosted zone if you have multiple zones with the same domain name.

5. DNS caching: Local DNS caches might still have old information. Try clearing your DNS cache.

To troubleshoot and resolve the issue:

1. Use the DNS Propagation Checker on whatsmydns.net to verify your record values across global locations.

2. If record values aren't consistent, ensure your TTL values are set to 60 seconds or less.

3. Review your previous DNS configuration and verify that all required records (A, CNAME, MX, TXT) are properly configured in Route 53 according to Shopify's requirements.

4. Use DNS troubleshooting tools like the "dig" command, DNSViz, or online DNS lookup tools to trace the DNS resolution and identify any failing name servers.

5. If the issue affects only specific DNS resolvers, you might need to contact your domain registrar for assistance.

6. Verify that your DNS Glue records match your NS records.

If you're still experiencing issues after 48 hours and after implementing these solutions, you may need to contact AWS Support for further assistance.
Sources
Troubleshoot DNS resolution issues for records in Route 53 public hosted zones | AWS re:Post
I changed DNS settings, but they haven't taken effect - Amazon Route 53
Dns Check after domain move shows only half success | AWS re:Post
Troubleshoot DNS propagation issues that occur after a domain transfer. | AWS re:Post
Resolve Amazon Route 53 CNAME records in public and private hosted zones. | AWS re:Post