amazon web services - How come I can't access AWS instance using Private DNS Address -


i set aws instance in vpc private ip address -- no public ip address. going mongodb instance , accessed other servers within vpc. established successful vpn connection , can ssh using putty instance using private ip address - "10.0.0.95". far, good. noticed private ip address has private dns - "ip-10-0-0-95.internal". tried using private dns access instance through vpn got putty error "unable open connection ip-10-0-0-95.ec2.internal. host not exist". clearly, can use 10.0.0.95 ip address surprised private dns name did not work. how come?

you should enable dns resolution vpc, or won't able resolve internal dns names.

to use private hosted zones, must set following amazon vpc settings true:

  • enablednshostnames
  • enablednssupport

steps enable dns resolution:

  • open amazon vpc console @ https://console.aws.amazon.com/vpc/.
  • in navigation pane, choose vpc.
  • select vpc list, choose actions , either edit dns resolution or edit dns hostnames (you should enable them)
  • in dialog box opens, choose yes, , save.

for more info: http://docs.aws.amazon.com/amazonvpc/latest/userguide/vpc-dns.html#vpc-dns-updating


Comments

Popular posts from this blog

javascript - Clear button on addentry page doesn't work -

c# - Selenium Authentication Popup preventing driver close or quit -

tensorflow when input_data MNIST_data , zlib.error: Error -3 while decompressing: invalid block type -