, queries to the Amazon provided DNS server at the 169.254.169.253 IP address, or the reserved IP address at the base of the VPC IPv4 network range plus two will succeed. in a VPC created on the Your VPCs page of the VPC console or using the AWS CLI, API, or an AWS SDK.The Amazon DNS server can resolve private DNS hostnames to private IPv4 addresses for all address spaces, including where the IPv4 address range of your VPC falls outside of the private IPv4 addresses ranges specified by RFC 1918.In Figure 2, we use the Get-Dns Server Resource Record cmdlet to query that DNS zone on the domain controller called DC.Figure 2 shows that the cmdlet successfully retrieved DNS records from a DNS zone.An Amazon-provided private (internal) DNS hostname resolves to the private IPv4 address of the instance, and takes the form is the reverse lookup IP address).You can use the private DNS hostname for communication between instances in the same network, but we can't resolve the DNS hostname outside the network that the instance is in.Important If you created your VPC before October 2016, the Amazon DNS server does not resolve private DNS hostnames if your VPC's IPv4 address range falls outside of the private IPv4 addresses ranges specified by RFC 1918.If you want to enable the Amazon DNS server to resolve private DNS hostnames for these addresses, contact AWS Support.
A DNS hostname is a name that uniquely and absolutely names a computer; it's composed of a host name and a domain name.
For this article, we will use an Active Directory domain called mylab.local.
The mylab.local DNS zone already exists on the domain controller.
DNS servers resolve DNS hostnames to their corresponding IP addresses.
Public IPv4 addresses enable communication over the Internet, while private IPv4 addresses enable communication within the network of the instance (either EC2-Classic or a VPC).