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

Add sub-zone dnskey check on adding new dnskey to a domain #1897

Closed
vohmar opened this issue Mar 30, 2021 · 0 comments · Fixed by #2206
Closed

Add sub-zone dnskey check on adding new dnskey to a domain #1897

vohmar opened this issue Mar 30, 2021 · 0 comments · Fixed by #2206
Assignees

Comments

@vohmar
Copy link
Contributor

vohmar commented Mar 30, 2021

On EPP/REPP domain update with adding new DNSKEY to domain object we should run the sub-zone check to make sure the key being added matches the key available in the authoritative nameservers. Delayed job should be added for new domain regsitrations and domain updates for configurable delay to check the validity of the trust-chain after the the change is made in registry.

if validation fails for all the host records then remove the key from the .ee zone

if validation fails for some of the hosts then the results should be configurable:
option 1: remove the host record from the .ee zone that does not have the valid dnskey record
option 2: remove the dnskey from .ee zone

Inform registrar via epp poll and domain contacts via email about the changes made to the registration

Key checking utility is available with the CSYNC functionality

Error message to return on failed check:

2308 "Data management policy violation: DNSKEY does not match or not found in the authoritative nameservers"

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

Successfully merging a pull request may close this issue.

2 participants