THE AWS CERTIFIED ADVANCED NETWORKING – SPECIALTY EXAM OBJECTIVES COVERED IN THIS CHAPTER MAY INCLUDE, BUT ARE NOT LIMITED TO, THE FOLLOWING:
Objective 2.3: Implement complex hybrid and multi-account DNS architectures.
In this chapter, we will expand on the DNS and Route 53 topics covered in Chapter 2, “Domain Name Services,” with the primary focus on implementing Route 53 and its features. We will use the AWS web console and configure the many features of Route 53. Since owning a domain name and hosting it on Route 53 is a chargeable service, you will have to decide whether you want to purchase your own domain or just follow along with the examples in this chapter.
You will gain skills in configuring Route 53 zones, records, traffic management, and security, as well as how to work with centralized and decentralized configurations and how to set up Route 53 monitoring and logging. With this practical knowledge, you will have the skills to answer the DNS objectives on the exam and also to work with Route 53 in the real world.
When working with standard DNS applications, you will configure zone files. A zone file is a collection of records that are managed as a group and belong to a single domain name. In Route 53, the concept is the same, but the name is slightly different as it is referred to by AWS as a hosted zone. A hosted zone is a container that contains the various types of DNS records. The hosted zone is part of a domain or subdomain such as tipofthehat.com or production.tipofthehat.com. The hosted zone and domain share the same name in the AWS Route 53 console, as shown in Figure 3.1.
FIGURE 3.1 Route 53 hosted zones
Hosted zones are either external and public-facing or internal to an AWS VPC, called a private zone. Public and private hosted zones are defined when configuring the zones in the Route 53 console, CLI, or API.
In Chapter 2, you learned that private hosted zones are used to store records for your internal, non-Internet hosts. Route 53 will respond to queries that are for resources running inside your VPC. Every zone can support services and servers in multiple VPCs if the zone is associated with the VPC. The private hosted zone is used strictly to route internally in your VPC and can connect to services such as ELB, an EC2 instance, or any service that has an IP address endpoint. Once the private hosted zone is created, resource records can be added to define your endpoints.
To route traffic inside your VPC using DNS, you must create a private hosted zone, as shown in Figure 3.2, and place the resource records inside of the zone.
Acedexam Training Policies
Learning resources
Other resources
Our Training Providers
