Route 53 domain dns not propagating

The issue you're experiencing with DNS propagation for your Route 53 registered domain is not uncommon, but there are a few things to check and steps you can take:

1. Nameserver Mismatch: There appears to be a mismatch between the nameservers you've set in Route 53 and the ones currently being used for your domain. The dig and whois results show different nameservers than the ones you've set in Route 53. This mismatch is likely the primary reason for the lack of propagation.

2. Update Nameservers: Ensure that the nameservers in your domain registration settings match exactly with those in your Route 53 hosted zone. You may need to update the nameservers in the domain registration section of Route 53 to match those in your hosted zone.

3. Propagation Time: Even after correcting the nameserver settings, it can take up to 48 hours for DNS changes to propagate globally. This is because DNS resolvers cache information and only request updates periodically.

4. Verify Hosted Zone: Double-check that your hosted zone in Route 53 is correctly set up with the A and CNAME records you mentioned.

5. Check for Multiple Hosted Zones: Ensure you don't have multiple hosted zones for the same domain, which could cause confusion.

6. TTL Values: Review the Time-to-Live (TTL) values on your DNS records. Lower TTL values can help speed up propagation, but remember that some resolvers might cache information for longer periods.

7. Use Route 53 Nameservers: Make sure you're using the Route 53 nameservers provided when you created the hosted zone, not any previous or external nameservers.

Unfortunately, there's no way to force an immediate global DNS propagation. The best approach is to ensure all your settings are correct in Route 53 and then wait for the propagation to complete naturally, which can take up to 48 hours.

If after 48 hours and verifying all settings you're still experiencing issues, it may be worth considering contacting AWS support for further assistance, as they can provide more in-depth troubleshooting for your specific case.
Sources
DNS Propagation Issues with Domain Registered in Route 53 - No Propagation After 48 Hours | AWS re:Post
I changed DNS settings, but they haven't taken effect - Amazon Route 53
Domain transferred to route53 but not propagated after five days | AWS re:Post
SOA Record from Route57 register domain cannot be found by DNSchecker.org | AWS re:Post

In this bit of your output, 86400 refers to the TTL (time-to-live) value in seconds, which equates to 24 hours:

$ dig NS doc-convert.co.za @nsza.is.co.za
.
.
.
;; AUTHORITY SECTION:
co.za.                  86400   IN      NS      coza1.dnsnode.net.
co.za.                  86400   IN      NS      ns2us.dns.business.
co.za.                  86400   IN      NS      ns.coza.net.za.
co.za.                  86400   IN      NS      ns0.is.co.za.

So it may take up to this amount of time for any changes to propagate to all nameservers around the world.

Current status https://dnschecker.org/#NS/doc-convert.co.za

Consider changing the TTL to a lower value to get it to propagate quicker.