Give your website a memorable name — Route 53

Your goal

Help visitors find a website by typing a name.

Why this matters

People remember names better than network addresses. You will connect a name to an endpoint, learn why changes take time, and separate DNS from hosting.

Words you will use

DNS is the internet’s name lookup system. A DNS record gives an answer for a name. TTL is how long a cached answer may be kept.

How to proceed

Read each situation and choose an answer. The lesson explains the result. Try again if needed, then continue through all three decisions and finish the tour.

1. Point a name at the site

Your app runs behind an AWS load balancer. You want example.com to lead visitors there. Choose the Route 53 record idea.

What should the DNS setup do?

Create a suitable alias record pointing to the load balancer.

Route 53 alias records can point a domain to supported AWS resources such as a load balancer. The app still runs at that endpoint; DNS only helps visitors find it.

The domain name points to the intended web entry point.

example.com → Route 53 alias → load balancer

2. Understand an old answer

You changed a DNS record. Some visitors still use an earlier answer held in a cache. Choose the setting that helps explain how long an answer may stay cached.

What should you inspect?

The DNS answer’s TTL.

TTL means time to live. Resolvers can keep an answer for that period. Changing a record does not instantly erase every cached answer, so plan DNS changes with that delay in mind.

You allow for cached DNS answers when planning a change.

Record change → cached old answers expire → new lookups

3. Separate finding from serving

The domain points to the right endpoint, but the website is down. Someone suggests putting the app’s source code into DNS. Choose the next useful check.

What still needs to work after DNS answers?

The app endpoint, its network access, and its web server.

DNS finds an endpoint. It does not run the application or make a failed web server healthy. Test the endpoint and follow the request path.

You investigate hosting and connectivity after checking the name lookup.

DNS lookup → network connection → web app response

Practice, then check your understanding

In the interactive tour, make each decision before seeing the outcome. Wrong answers receive coaching, and replay gives you a fresh attempt without duplicating earned XP.

Read the official AWS documentation for service behavior and production details.