DNS Propagation

Hi, As a quick background: Last year we bought a domain from GoDaddy later transffered it to AWS to be our registrar. We had the NS records for AWS and it was fine. We are also connected to Office365, which required us to update the NS records to microsoft ones and modify TXT and MX records.

The issue is that there are some moments, where for a few people in specific domains, they cannot access the domain/website. The domain name cant be resolved at all and it causes multiple issues. It occurs every once in a while and consistently on some networks.

When we run the dig command with the GTLD, we get (not disclosing domain due to privacy issues):

<DOMAIN>.          172800  IN      NS      ns-641.awsdns-16.net.
<DOMAIN>.          172800  IN      NS      ns-411.awsdns-51.com.
<DOMAIN>.          172800  IN      NS      ns-1689.awsdns-19.co.uk.
<DOMAIN>.          172800  IN      NS      ns-1192.awsdns-21.org.

and they are still pointing to the old records, whereas other major public DNS services already have the correct updated information:

~$ dig <domain> @1.1.1.1 NS +short
ns4.bdm.microsoftonline.com.
ns1.bdm.microsoftonline.com.
ns2.bdm.microsoftonline.com.
ns3.bdm.microsoftonline.com.
~$ dig <domain> @8.8.8.8 NS +short
ns1.bdm.microsoftonline.com.
ns2.bdm.microsoftonline.com.
ns3.bdm.microsoftonline.com.
ns4.bdm.microsoftonline.com.
~$ dig <domain> @9.9.9.9 NS +short
ns1.bdm.microsoftonline.com.
ns2.bdm.microsoftonline.com.
ns3.bdm.microsoftonline.com.
ns4.bdm.microsoftonline.com.

Why has this change not propagated and how can we get around to fixing this?

Cheers