Skip to content
This repository has been archived by the owner on Jun 5, 2020. It is now read-only.

Can't handle public and private Route53 zones with the same domain name #523

Open
Azolo opened this issue Jan 11, 2019 · 0 comments
Open

Comments

@Azolo
Copy link

Azolo commented Jan 11, 2019

There are instances where Public records are different than the Private records.

Unfortunately the current implementation doesn't know how to handle the situation where there is a public zone and a private zone, with a vpc attachment, that both use the same domain name(e.g. example.com.).

It may not be a case worth handling, but it is an unhandled case.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant