0

Unless I am asking the question incorrectly or using the incorrect terminology, there seems to be no information on how to setup Route53 to delegate a DNS zone to an EC2 instance. Or maybe it's just impossible?

The use case is simple. Due to very specific requirements I must host a private DNS zone with BIND on an EC2 instance. However I would like all the other stuff in my VPC to resolve hostnames in that zone while still using the VPC's default resolver.

I tried looking at the "Resolver Rules" section. When I select the forward option I can add a domain name and IP address, but it also needs an Outbound endpoint. When I go to create an Outbound endpoint It says:

An outbound endpoint contains the information that Resolver needs to route DNS queries to your network from your VPCs

That's not what I am doing. The DNS queries are going to remain in the same VPC.

Worst case is I spin up my own DNS resolver cluster on EC2 and disregard Route53 completely, but that seems like overkill.

1
  • I went ahead and tried adding the outbound endpoint and used that in the forward rule. It 'works', but is this the correct way to do it?
    – Tuaris
    Jan 5 at 16:02

0

You must log in to answer this question.

Browse other questions tagged .