Name Server has not correctly transferred from UK2 to AWS Route53

I understand your frustration with the domain transfer process. Let me explain what might be happening and what you can do to resolve this issue.

When you transfer a domain to Amazon Route 53, it can take up to 48 hours (2 days) for the change to take effect across the internet. This is because DNS resolvers typically cache the name server information and only request updates every two days. Since your transfer was completed three days ago, we should investigate further.

Here are some steps you can take to troubleshoot and resolve the issue:

1. Verify the name servers: In the Route 53 console, go to the "Registered domains" section and check the name servers listed for your domain (signagelivemail.com). Make sure they match the name servers in your Route 53 hosted zone.

2. Update name servers if necessary: If the name servers don't match, you'll need to update them. In the Route 53 console, go to the domain's details, choose "Edit name servers" from the Actions drop-down, and update them to match your hosted zone's name servers.

3. Check DNS propagation: Use online DNS lookup tools to check if the new name servers are visible across the internet. It may take some time for all DNS resolvers to update their cached information.

4. Verify records: Ensure that all necessary DNS records (such as A, CNAME, MX records) are correctly set up in your Route 53 hosted zone.

5. Contact AWS Support: If you've verified all the above and are still experiencing issues, it would be best to contact AWS Support for further assistance. They can help investigate any potential issues with the domain transfer or DNS configuration.

Remember, even though UK2 says they can't help, the transfer process should have been completed on their end. If Route 53 shows that the domain is now registered with AWS, then you're on the right track, and it's likely just a matter of DNS propagation or configuration within Route 53.

Be patient, as DNS changes can sometimes take longer than expected to propagate fully. If the issue persists beyond 5-7 days, definitely escalate to AWS Support for a more in-depth investigation.
Sources
I changed DNS settings, but they haven't taken effect - Amazon Route 53
Updating name servers to use another registrar - Amazon Route 53
Making Route 53 the DNS service for a domain that's in use - Amazon Route 53

Ah, interesting, I did not know my NS on my actual domain would change back to the old registrar - shame they did not auto-update during the NS transfer - thanks for your help.