Hi, @Ntention. The DNS is configured incorrectly currently.
As, @gregraven already mentioned, I’m also showing both Netlify DNS and AWS Route 53 being used at the same time. Unless you have some advanced custom tooling to keep the two DNS services in sync, this is unlikely to be successful.
So, before proceeding, we will need to confirm which DNS service you will use (or if you plan to use both how that is being done). Would you please confirm which DNS service is the one you want to use?
After determining that, the next step would to be make sure only the chosen DNS service is configured for the domain at the registrar. Also, if you query Route 53, you can see that the TTL (time to live) is 48 hours (172800 seconds):
$ dig +noall +answer @ns-85.awsdns-10.com ntention.com NS
ntention.com. 172800 IN NS ns-1264.awsdns-30.org.
ntention.com. 172800 IN NS ns-1658.awsdns-15.co.uk.
ntention.com. 172800 IN NS ns-85.awsdns-10.com.
ntention.com. 172800 IN NS ns-864.awsdns-44.net.
This means that when the changes are made at the registrar, it can take as long as 48 hours for the previous records to be removed from the caches of DNS resolvers around the world.
If you still see issues after moving to a single DNS service, please let us know which records are not working the the IP address for the resolver returning the wrong or missing record responses.