Understand the resolver cache
A DNS lookup is not necessarily repeated for every visit. Resolvers cache answers for the record's TTL, and a visitor's device or network may continue using an answer it already received. Changing the record at IaGenify updates the zone, but it cannot instantly clear every cache elsewhere on the internet.
The time to live is the maximum caching interval indicated for that record, not a guaranteed global propagation countdown. Some resolvers refresh sooner, while others may retain an answer until its cache expires. A change can therefore appear at different times across networks even when the authoritative zone already shows the new value.
Check the authoritative record and wait through the TTL
First confirm that the record name, type, and destination are correct in the active IaGenify DNS zone, and check that the domain uses the intended nameservers. If the authoritative data is wrong, waiting will not fix the configuration. Compare lookups from more than one resolver to see whether the old response is cached only in certain places.
Once the authoritative answer is correct, allow the previous TTL window to pass before treating remaining old responses as a new fault. Lowering a TTL in advance can shorten a planned future change, but it does not erase caches that already stored the old TTL. Avoid repeatedly changing the destination while caches are still refreshing, since that makes the observed result harder to interpret.