- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Hello.
Maybe it has something to do with the TTL of the record?
If the TTL value is large, new IP addresses may not be resolved for several minutes.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/best-practices-dns.html
Does the issue need manual operation to resolve? Or, after waiting several minutes/hours, is the issue resolved automatically? If so (automatically resolved issue), DNS record have Time To Live and Propagation mechanism and it cause the issue. Change for DNS record often need time to reflect the change to name resolution by local machines.
I have not been able to resolve the issue so far (i.e. permanently delete the records) either manually or by waiting. The change is initially effective but reverts to the previous ip address after a few minutes.
In the end I deleted the hosted zone and created a new one with the entries I wanted to keep.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor einem Jahr- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
I was wondering the same thing, it's roughly the right amount of time. The TTL is set to 300 of the deleted records was set to 300 and the records reappeared 280s after deletion.