There are many hooks and integrations between the many AWS service offerings. Since Route 53 is a very fundamental networking service that is used extensively within AWS to route traffic, there are many features added to Route 53 to integrate features and make configurations easier for the customer. Amazon does not charge for Alias queries for internal services, which is nice.
DNS is supported in a VPC using Route 53’s resolver features. Since Route 53 is a global service, its servers sit outside of the VPC using the IP address of 169.254.169.253, which is the base CIDR IP of the VPC’s subnet +2. So, if you have a subnet of 172.16.200.0 /24, the DNS IP address would be 172.16.200.2. If the instance is configured with a private IP address, AWS will assign a hostname and IP address and register with DNS. If it is a public IP, then a public hostname will be registered along with its public IP address. Route 53 creates a private hosted zone for name resolution. Network access control lists and security groups will not work as filters of Route 53 communications, and the Route 53 Resolver only supports recursive lookups.
For public name resolution, DNS default names are in two different formats. The first for the us-east-1 (Virginia) region looks like ec2-<public IP address>-compute-1.amazonaws.com; for all other regions, it will be ec2-<public IP address>-region.compute.amazonaws.com. Each EC2 instance can query at a rate of 1,024 packets per second. When this quota is exceeded, the service is throttled.
The resolver matches the public domain name with the public IP address of the outside instance interface and to the private IP of the inside, or private, instance interface.
To support public name resolution, the enableDnsHostnames attribute enables assigning public DNS hostnames to instances with public IP addresses. This attribute is enabled by default for the default VPC and disabled for all other VPCs. enableDnsSupport, enabled by default, allows the use of the Amazon DNS service in the VPC. Virtual machine interface address and names can be obtained through the web GUI under EC2, the CLI using the describe-network-interfaces command, and in PowerShell using the Get_EC2VpcAttribute command.
Route 53 is integrated with CloudFront using routing policies including latency, geo-based, and failover routing. Zone apex support allows you to access your CloudFront edge locations using the apex name of, for example, tipofthehat.com along with www.tipofthehat.com. Alias records allow you to use your company domain name in place of the more convoluted AWS CloudFront names.
The use of the Alias record is also used in directing traffic via Route 53 to the Elastic Load Balancing (ELB) service. Since the ELB address is a domain, an Alias can be configured to point your company’s domain name to the AWS load balancer virtual server’s DNS name. These integrations work for all of the different ELB offerings.
Acedexam Training Policies
Learning resources
Other resources
Our Training Providers
