We're evaluating Neorouter pro in order to provide backoffice users access to web apps hosted inside an AWS VPC. I've been able to get this working fine, however, the DNS resolution for commands like ping or using the Web app are trying to use what I assume is the server's "public IP" for peer to peer access, rather than the private network address which in our case is configured as 192.x.x.x.
I basically just want to be able to use the server name or alias and have it resolve to 192.x.x.2 which is the server's assigned DHCP IP.
How can I achieve this transparently, or do I have to maintain my own DNS server?
|