Check the record before diagnosing propagation
First confirm that the record was saved on the DNS zone that is actually authoritative for the domain. Check the exact host, record type, and target value, then query the result through more than one resolver. If the configured record itself is wrong, waiting will not correct it.
If the authoritative value is correct but some networks still return an earlier answer, caching is a likely explanation. A browser, operating system, local network, or recursive resolver may retain a previous result. Compare the returned values and the time of each check so you can tell whether the old answer is gradually disappearing.
Avoid repeated edits while caches update
Repeatedly changing a record because one device still sees an earlier answer can make the transition harder to understand. Keep a note of the intended value and the time you changed it, then check at reasonable intervals from different networks. Test the service itself as well as the DNS lookup, since a correct record does not guarantee that the destination application is ready.
If results remain inconsistent beyond the expected cache period, inspect the authoritative nameservers and confirm they all serve the intended zone. Check for duplicate or conflicting records and verify the hostname the client is requesting. Escalate with the hostname, record type, observed answers, and timestamps rather than only reporting that DNS is slow.