Domain partially suspended after contact information not verified and then fixed

Based on the information provided, it seems you've encountered a complex issue with your domain's DNS propagation after resolving a contact verification problem. Here are some potential reasons and steps you can take to address the situation:

1. Partial DNS propagation: Even though the TTL for your NS records is 2 days, some DNS resolvers might still be caching old information. This is unusual after several weeks, but it's not impossible.

2. Multiple hosted zones: Check if you have multiple hosted zones with the same name in Route 53. If you do, ensure that the correct hosted zone is associated with your domain registration.

3. Name server inconsistency: Verify that the name servers listed in your Route 53 hosted zone exactly match those listed in your domain registration. Even a small discrepancy can cause issues.

4. Domain suspension lingering effects: Although you've resolved the contact verification issue, there might be lingering effects from the domain suspension. Some DNS resolvers might still be using cached information from when the domain was suspended.

5. Registry-level issues: There could be issues at the registry level that are causing inconsistent propagation of your NS records.

To address these potential issues, you can try the following:

1. Double-check your Route 53 configuration to ensure all settings are correct.

2. Contact AWS Support to verify that there are no remaining issues related to the previous suspension and that everything is correctly configured on their end.

3. Consider creating a new hosted zone and updating your domain registration with the new name servers. This might help "reset" the DNS propagation process.

4. Monitor your domain's availability using Route 53's query logging or third-party monitoring services to track improvements.

5. If the issue persists, you may need to escalate the case with AWS Support or even contact your domain's registry to ensure there are no issues on their end.

Remember that DNS changes can sometimes take longer than expected to fully propagate, but several weeks is unusually long. Persistent issues likely indicate an underlying configuration problem that needs to be addressed.
Sources
My domain is unavailable on the internet - Amazon Route 53
I changed DNS settings, but they haven't taken effect - Amazon Route 53
My domain is suspended (status is ClientHold) - Amazon Route 53