CODEWITHSUNDEEP
amazon-web-servicesamazon-ec2
wheresmycookie
wheresmycookie

Reputation: 763

Private DNS not resolving for EC2 instance

I just set up a VPN server using OpenVPN on an Amazon EC2 instance using this tutorial: https://hackernoon.com/using-a-vpn-server-to-connect-to-your-aws-vpc-for-just-the-cost-of-an-ec2-nano-instance-3c81269c71c2.

When I connect to my VPN server, the problem that I'm experiencing is that I am unable to connect with the private DNS:

$ssh -i X.pem [email protected]
ssh: Could not resolve hostname ip-172-31-aa-bbb.ec2.internal: nodename nor servname provided, or not known

However, when I use the private IP address (still on the VPN):

$ssh -i X.pem [email protected]
Last login: Thu Mar 22 18:43:34 2018 from 172.31.aa.bbb

       __|  __|_  )
       _|  (     /   Amazon Linux AMI
      ___|\___|___|

Would I be required to use a private hosted zone to achieve this? If so, is this something I can use alongside my current DNS provider (Hover)? I feel like I'm lacking a basic understanding of how this private hosting works, so details would be appreciated.

Upvotes: 4

Views: 3135

Answers (1)

Mukesh Kumar
Mukesh Kumar

Reputation: 11

You need to append suffix in DNS at OS level

enter image description here

for detail please refer to URL: https://docs.aws.amazon.com/quickstart/latest/active-directory-ds/ad-design.html

Upvotes: 1

Related Questions