- Newest
- Most votes
- Most comments
Hi,
Your instance can forward DNS request to the IP address of the Amazon-provided DNS server for your VPC. Amazon DNS server cannot resolve private DNS hostnames if you do not set the following attributes to true:
• enableDnsHostnames: Indicate whether instances with public IP get corresponding public DNS hostnames.
• enableDnsSupport: If this attribute is false, Amazon provided DNS server that resolves public DNS hostnames to IP addresses is not enabled.
For more information, please refer to this article [1].
To create a private hosted zone using the route 53 console follow this link [2].
[1]- https://docs.aws.amazon.com/vpc/latest/userguide/vpc-dns.html#vpc-dns-support
[2]- https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zone-private-creating.html
Regards
/Bennie
Those things are set up. I can ping it's full name but not the shortname within the VPC. This is for a private hosted zone
works
ping instancename.domain.name
doesnt work
ping instancename
Edited by: witchkinkofangmar on Oct 18, 2019 9:08 AM
I actually just added one line in resolv.conf to get it working.
search ec2.internal
search domain.name
nameserver 10.26.50.2
nameserver ns-1536.awsdns-00.co.uk
nameserver ns-0.awsdns-00.com
nameserver ns-1024.awsdns-00.org
nameserver ns-512.awsdns-00.net
I thought since our VPC options were set to domain-name = ec2.internal; I wouldn't need to add the search base
Relevant content
- asked a year ago
- asked 7 months ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago