Which DNS name can only be resolved within Amazon EC2?
A.
Internal DNS name
B.
External DNS name
C.
Global DNS name
D.
Private DNS name
Get 50% Discount on All Your Purchases
at PrepAway.com - Latest Exam Questions
This is ONE TIME OFFER
50%
A – WITHIN AWS
0
0
A.
0
0
Hey !!!
Its Private DNS, Ans: D
3
0
Using Private Hosted Zones
If you want to access the resources in your VPC using custom DNS domain names, such as example.com, instead of using private IP addresses or AWS-provided private DNS hostnames, you can create a private hosted zone in Amazon Route 53. A private hosted zone is a container that holds information about how you want to route traffic for a domain and its subdomains within one or more VPCs without exposing your resources to the Internet. You can then create Amazon Route 53 resource record sets, which determine how Amazon Route 53 responds to queries for your domain and subdomains. For example, if you want browser requests for example.com to be routed to a web server in your VPC, you’ll create an A record in your private hosted zone and specify the IP address of that web server. For more information about creating a private hosted zone, see Working with Private Hosted Zones in the Amazon Route 53 Developer Guide.
1
0
D
0
0
Should be D
0
0
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-dns.html
it’s D
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.
0
0
D is the right answer.
See http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zones-private.html
A private hosted zone is a container that holds information about how you want to route traffic for a domain and its subdomains within one or more Amazon Virtual Private Clouds (Amazon VPCs).
3
0
D.
A private (internal) DNS hostname resolves to the private IPv4 address of the instance, and takes the form ip-private-ipv4-address.ec2.internal for the us-east-1 region, and ip-private-ipv4-address.region.compute.internal for other regions (where private.ipv4.address 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.
0
0
A
The internal DNS name can only be resolved within Amazon EC2
http://www.wangzhongyuan.com/archives/737.html
http://stackoverflow.com/questions/10434101/why-might-the-cidr-ip-in-db-security-group-be-different-from-instance-elastic-ip
0
0
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-dns.html
A private (internal) DNS hostname resolves to the private IPv4 address of the instance
To view DNS hostnames for an instance using the console
1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.
2. In the navigation pane, choose Instances.
3. Select your instance from the list.
4. In the details pane, the Public DNS (IPv4) and Private DNS fields display the DNS hostnames, if applicable.
In the AWS documentation (Internal) is used in brackets which indicates that it is for clarification purposes, you can also see that in the console the address is under Private DNS
For this reason the anser is D
1
0
Correct answer is A
0
0
Guys, The Correct answer is A.
Amazon EC2 also provides an internal DNS name and a public DNS name that map to the private and public IP addresses, respectively. The internal DNS name can only be resolved within Amazon EC2. The public DNS name resolves to the public IP address outside the Amazon EC2 network, and to the private IP address within the Amazon EC2 network.
0
0
Both A and D are correct.
A private (internal) DNS hostname resolves to the private IPv4 address of the instance, and takes the form ip-private-ipv4-address.ec2.internal for the us-east-1 region, and ip-private-ipv4-address.region.compute.internal for other regions (where private.ipv4.address is the reverse lookup IP address).
0
0
D.
Private DNS name
0
0
A !!!
When you launch an instance, we allocate a private IPv4 address for the instance using DHCP. Each instance is also given an internal DNS hostname that resolves to the private IPv4 address of the instance; for example, ip-10-251-50-12.ec2.internal. You can use the internal 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.
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html
0
0
this is confusing. Even in AWS Documentation they are using both “Internal DNS hostname” and “Private DNS hostname” at different locations.
Here are the links:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html
which says- ” When you launch an instance, we allocate a private IPv4 address for the instance using DHCP. Each instance is also given an internal DNS hostname that resolves to the private IPv4 address of the instance; for example, ip-10-251-50-12.ec2.internal. You can use the internal 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.”
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-dns.html
which says – ” 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.
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.”
Now i am confused..
0
0
I think D…
An Amazon-provided private (internal) DNS hostname resolves to the private IPv4 address of the instance, and takes the form ip-private-ipv4-address.ec2.internal for the us-east-1 region, and ip-private-ipv4-address.region.compute.internal for other regions (where private.ipv4.address 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.
Source: http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-dns.html
0
0
D.
In the details pane, the Private DNS (IPv4) field displays the private DNS hostname.
0
0
D
0
0
Is private DNS hostname/name and internal DNS hostname/name different ?
private DNS hostname can be resolved by Route53 as well, so internal DNS hostname can ONLY be solved in EC2 ??
the question i guess is focus on ONLY.
0
0
Answer for this question is A as it stresses on ‘within EC2. ‘private DNS name’ is associated to Route 53
https://aws.amazon.com/about-aws/whats-new/2014/11/05/amazon-route-53-now-supports-private-dns-with-amazon-vpc/
1
0