Before you start: Review IP addresses, subnets and DNS if they are new to you.
What to aim for
Distinguish cloud service models and shared responsibility.
Explain the roles of EC2, S3, VPC, Route 53 and Lambda.
Try it yourself: Sketch a VPC, subnet and EC2 instance, then explain the route and access controls needed for internet connectivity. A drawing needs no cloud account.
Suggested preparation, not an entry requirement. Every track stays free to open.
Learn with Network Kings videos, ordered chapters and practical explanations. Choose a subject to see what to study and which lessons to watch first.
A little time. A new idea.
Bite-sized tech lessons from the channel
CCNP & CCIE
286 views
Explore more
452 views
Networking
353 views
CCNP & CCIE
2.3K views
Networking
1K views
Networking
599 views
Linux & DevOps
620 views
Networking
363 views
Explore more
368 views
Networking
608 views
Explore more
489 views
AWS
315 views
Video · AWS
Your browser paused autoplay. Press Play inside the video to start.
AWS Tutorial - AWS Route 53 | AWS Route 53 Tutorial | What Is AWS Route 53?
AWS · 52:26
LEARNING CHAPTER
Understand. Remember. Apply.
AWS Route 53
DNS records
Hosted zones
DNS caching
Based on the video transcript
Connect a domain to an EC2 website with Route 53
The lesson explains Route 53, DNS lookup and common record types, then builds a simple website example. The practical begins around 18:28 with an EC2 web server, tests the website by its public IP and associates an Elastic IP. From about 33:24, it creates a public hosted zone and an A record, then updates the domain registrar's name servers to delegate DNS to Route 53. The final discussion shows different clients beginning to resolve the name as the changes take effect. Failover, weighted and geolocation routing are introductions for later classes, not completed labs in this recording.
Key takeaways
Keep the domain registrar, authoritative DNS service and web host separate: DNS returns address information, while the browser connects to the website's server.
The public hosted zone gets NS and SOA records automatically. The registrar must delegate to the hosted zone's assigned name servers for public queries to reach it.
The demonstration checks HTTP access by public IP before configuring DNS, then associates an Elastic IP with the EC2 instance to provide a stable address for the record.
A records hold IPv4 addresses; AAAA records hold IPv6 addresses. CNAME records refer to another DNS name, while MX records identify mail servers.
The lab uses a simple-routing A record for its one web server and adjusts TTL. Cached answers can delay what a client sees; changing DNS does not instantly refresh every resolver.
Put it into practice
On paper, use example.com and a documentation address such as 192.0.2.44. The website opens by IP, and its A record is correct in a new hosted zone, but the registrar still lists the old name servers. Identify the missing DNS step. After fixing the delegation, explain why one client might still see an older address and which cached information you would check before changing the web server.
Explore the diagram / topology
Illustrative concept diagram for study.
Separate setup from traffic. The dotted arrow represents the registrar's delegation setting, not a request passing through the registrar. DNS supplies an address; the browser then requests the website from the web server. A cached answer may be reused until its TTL expires. Root and TLD lookups are omitted for clarity. This uses the lesson's paper example, example.com and 192.0.2.44, rather than its exact lab domain or server address. If the site opens by IP but not by name, compare delegation, the A record and cached answers before changing the web server.
8 lessons
