Route53 Time to Live

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or

Already have an account? Sign In »

Time
19 hours 19 minutes
Difficulty
Intermediate
CEU/CPE
20
Video Transcription
00:00
>> Hey everybody and welcome back.
00:00
In this lecture, we're going to talk about
00:00
Route 53 Time to Live service.
00:00
This learning objective is going to be
00:00
to define the concept of time to live.
00:00
We want to make sure you
00:00
understand what that is and then we'll
00:00
discuss how that's relevant to Route 53.
00:00
Time to live refers to the time it takes for an object
00:00
to be set or stored before it is deleted or refreshed.
00:00
It's the time that it takes before
00:00
something changes or how long it takes for it to change.
00:00
The reason why this is done is
00:00
because you want to provide a margin
00:00
of time to allow
00:00
for changes to propagate across the Internet.
00:00
DNS is something that's a service
00:00
that the global worldwide web uses.
00:00
You have multiple DNS servers across
00:00
the globe that are going to feed off
00:00
of these changes and see how these time to live timer
00:00
is in place to allow for that flow of traffic.
00:00
This taking turns between
00:00
all the different changes that take
00:00
place across the entire Internet.
00:00
It doesn't just apply to the Internet,
00:00
it can also apply to other things as well.
00:00
But in reference to this,
00:00
that's how that works.
00:00
The best way to define this is,
00:00
let's say you're making a change to your DNS records,
00:00
you're changing the host web server IP address.
00:00
Let's say you have an old website,
00:00
it's running on an old server
00:00
and you recently built a new one.
00:00
The server for the new one is different,
00:00
different IP address.
00:00
You can change the DNS record to
00:00
point to the new IP address for the new website server.
00:00
There's going to be a time to live
00:00
for how long it takes for that change to take place,
00:00
how long it takes for that change to propagate.
00:00
That time to live can vary.
00:00
You can usually modify it,
00:00
but sometimes you can't,
00:00
depending on the registrar or
00:00
the place where you're making
00:00
the modification for the DNS record.
00:00
But that's essentially what it is.
00:00
TTL refers to the content caching.
00:00
How long it takes for the browsers,
00:00
when you type in your domain name and
00:00
it translate that to the new IP address,
00:00
there's going to be a caching period.
00:00
Time to live is going to
00:00
dictate how long that caching period is going to be taking.
00:00
That's just one very specific example.
00:00
This can be applicable in
00:00
other scenarios inside information technology.
00:00
When it comes to Route 53,
00:00
this is how it works.
00:00
You have a low TTL option and a high TTL option.
00:00
A low TTL is 60 seconds.
00:00
Very quick, your caching is not going
00:00
to be a very long term.
00:00
If you're making iterative changes
00:00
and you need to see what's going on,
00:00
you need to see if the change worked quickly,
00:00
low TTL is great for
00:00
that purpose because you can just make the modification.
00:00
You take a minute and you come back and
00:00
you can go in and see if the change was applicable.
00:00
This typically is going to cause
00:00
more traffic to Route 53 because of that.
00:00
But like I said, you're getting
00:00
less time and everything isn't going to be outdated,
00:00
so you'll be able to look at it sooner.
00:00
This makes it easy to make changes
00:00
to your records quickly.
00:00
The high TTL option has less traffic through 53 and it
00:00
can possibly lead to outdated records depending on
00:00
what's going on. That's it.
00:00
Within Route 53, you can modify
00:00
the TTL for whatever your needs are,
00:00
and then you could perform the testing appropriately.
00:00
Sixty second is something that I
00:00
typically leverage whenever I'm
00:00
building a website because I want to make
00:00
sure that it's pointing to
00:00
the right IP address and that
00:00
everything is working out just fine before I do that.
00:00
If you're setting up an Alias record,
00:00
it's going to require a TTL for each records.
00:00
Just keep that in mind.
00:00
To go ahead and wrap up, in this lesson,
00:00
we talked about the time to live,
00:00
how it works and how it's applicable to Route 53.
00:00
If you guys have any questions,
00:00
feel free to reach out to me and if not,
00:00
I'll see you in the next lecture.
Up Next