Yes, it helps, it's Private Hosted Zone which I need to use in this case. So is it mandatory to use a Route53 resolver in between or I can map api1.test.example.com and api2.test.example.com directly to my server's private ip on the remote DNS server?
Asking this because I tried both i.e., mapping directly to server's ip as well as mapping to resolver inbound endpoint ip, and what I see is that the former works but the latter doesn't. So any idea where am I going wrong?
As convenient as that would be, I would use Resolver. It will take additional setup. However, it will take less setup than the alternative which is to build your own DNS servers.
If you successfully accomplish your mission with the tools you have available to you, would you let me know? I could edit the article to discuss what Route53 can do regarding hybrid clouds.
Should you need additional help, I will be checking this website regularly.
Hi Arswaw,
Yes, it helps, it's Private Hosted Zone which I need to use in this case. So is it mandatory to use a Route53 resolver in between or I can map api1.test.example.com and api2.test.example.com directly to my server's private ip on the remote DNS server?
Asking this because I tried both i.e., mapping directly to server's ip as well as mapping to resolver inbound endpoint ip, and what I see is that the former works but the latter doesn't. So any idea where am I going wrong?
As convenient as that would be, I would use Resolver. It will take additional setup. However, it will take less setup than the alternative which is to build your own DNS servers.
If you successfully accomplish your mission with the tools you have available to you, would you let me know? I could edit the article to discuss what Route53 can do regarding hybrid clouds.
Should you need additional help, I will be checking this website regularly.
Sure, thanks for your help.