route53 private zone forward to public zone

0

Hi,

I just migrated a public DNS zone (example.com) to AWS Route53, everything works as excpeted. Now I want to create a private DNS zone for this domain. I've setup a private zone for example.com. My problem is: if I have an entry (onlypublic.example.com) in the public zone but not in the private zone, I won't be able to resolve that name from the VPC. It behave like the private zone says "I don't know that entry" without forwarding it to the public zone.

How could I achieve that ? I know that using a sub domain (xxx.private.example.com) for private entries would help, but I don't want to use that.

Before the migration to AWS, I used RPZ in Bind9 to acheive this.

Thanks !

edouard
질문됨 일 년 전713회 조회
1개 답변
1
수락된 답변

Hi,

Route53 currently does not have this capability. Depending on the volatility I can see two approaches to get you there:

  1. Duplication: If it is a single, static DNS entry your easiest approach might be to just duplicate the DNS entry to the private zone.
  2. Sync via additional automation: If there are multiple entries, or if they change regularly, an approach might be to write a custom Lambda which syncs the selected public entries to the private zone.

If this is cross account you might have issues with alias entries, as you cannot use them in an account where the resource does not reside.

전문가
답변함 일 년 전
profile picture
전문가
검토됨 일 년 전
profile picture
전문가
검토됨 일 년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠