Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[L3D] do not allow A/AAAA/PTR records in zone-profiles #238

Closed
miesi opened this issue Apr 27, 2022 · 0 comments
Closed

[L3D] do not allow A/AAAA/PTR records in zone-profiles #238

miesi opened this issue Apr 27, 2022 · 0 comments
Labels
cli related to the command-line interface enhancement New feature or request
Milestone

Comments

@miesi
Copy link
Contributor

miesi commented Apr 27, 2022

When zone-profiles are copied to become a real zone, the A and AAAA records must belong to layer3domain.

It is not feasible to specify on the layer3domain each A/AAAA record needs to go to when ndcli create zone is executed.

To avoid this problem, zone-profiles must not contain A or AAAA records.

@miesi miesi added enhancement New feature or request cli related to the command-line interface labels Apr 27, 2022
@miesi miesi added this to the next milestone Apr 27, 2022
@miesi miesi changed the title [L3D] do not allow A/AAAA records in zone-profiles [L3D] do not allow A/AAAA/PTR records in zone-profiles Apr 27, 2022
@Srudush Srudush closed this as completed in 6a3d32f Jun 3, 2022
Srudush added a commit that referenced this issue Jun 3, 2022
fix #238 - do not allow A/AAAA/PTR records in zone-profiles
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cli related to the command-line interface enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant