Erik DeBill is a user on wandering.shop. You can follow them or interact with them if you have an account anywhere in the fediverse.
If you don't, you can sign up here.
So if my website right now is a Route 53 domain name pointing to a static site hosted on S3, I can just delete the S3 bucket and point the domain at the new site and nothing will explode, right?
@srol sorry. Time To Live. It tells DNS servers how long they can cache DNS records for. It should be one of your Route 53 settings. Frequently it is set to a day or more, so it can take a long time for everyone to find out about a server change. I’m not sure what Amazon defaults it to.
@edebill@srol I wouldn't worry about it too much, unless it is a really busy server odds are not many people will have the current DNS answer cached. And usually the DNS servers that do the caching have a shorter maximum TTL.
In my experience around 4 hours is the longest you will usually wait for a domain to point to the new webserver.
Will you also change the email destination (MX-records)?
AWS question Show more
@edebill @srol
I wouldn't worry about it too much, unless it is a really busy server odds are not many people will have the current DNS answer cached. And usually the DNS servers that do the caching have a shorter maximum TTL.
In my experience around 4 hours is the longest you will usually wait for a domain to point to the new webserver.
Will you also change the email destination (MX-records)?