-
Notifications
You must be signed in to change notification settings - Fork 19
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
Implement Csync for CDNSKEY #1603
Conversation
56ee215
to
3e8eeb4
Compare
39d909c
to
2fa020c
Compare
96daaec
to
bbeaea9
Compare
f502626
to
7c6f5d9
Compare
on imoprt job execution, I get error: https://gist.github.com/ratM1n/3856a801e45328361b6ed2f723b9cca5 |
"generate" works as it should, but in import, i get this: https://gist.github.com/ratM1n/bc6601d530935f1093f7363d2478788a |
46b20bc
to
3c539aa
Compare
Before merging, please undo commit a53475d For testing, Ensure you use RAILS_ENV
|
6067ccd
to
a53475d
Compare
last change broke database query: https://gist.github.com/ratM1n/0e8ffabac7bf4010d7f3a7cd192268c3 |
e3d770b
to
fe6f5e8
Compare
fe6f5e8
to
15ce6d7
Compare
author Karl Erik Õunapuu <[email protected]> 1591359032 +0300 committer Alex Sherman <[email protected]> 1617029320 +0500 CsyncJob: Don't respect IPv6 if nessecary
448fae8
to
a6bb0f1
Compare
a6bb0f1
to
aa4c040
Compare
c08d0b6
to
56565d6
Compare
Closes #658
Requires cdnskey-scanner to be installed, so it can crawl cdnskeys of domain zone.
By default, when new CDNSKEY record is found, it is added to the zone if scanner & Job has gone through 3 cycles and the CDNSKEY data is persistent.
Required modifications to config/application.yml:
...where file specificed in
cdns_scanner_input_file
is the file which is used for STDIN ofcdnskey-scanner
binary andcdns_scanner_output_file
is the STDOUT ofcdnskey-scanner
.CsyncJob.run(generate: true)
can be used to generate content ofcdns_scanner_input_file
, but it can be created by external script as well. It's optional.CsyncJob.run
reads thecdns_scanner_output_file
line by line and keeps track of cycles and whether and when new CDNSKEY can be pushed to zone as DNSKEY.It is expected that
CsyncJob.run
is ran aftercdnskey-scanner
has processed the data and successfully outputed data tocdns_scanner_output_file
. Output file must be not modified.It is expected that
CsyncJob.run
is triggered only once per eachcdnskey-scanner
output. Each job run is considered as 1 cycle. As mentioned before, 3/3 cycles triggers the update of zone if the domain doesn't have active DNSSEC data or instantly after first run if it does.Launch of
cdnskey-scanner
is not implemented in this PR as the scanning process itself is time consuming. But generally something like this via Cron should work:Better logging
Send poll message when DNSSEC data changed for domain
Notify registrant if DNSKEY has been added/deleted from zone
cdnskey 0 3 0 AA== (remove)
Validate DNSSEC doesn't break with new soon-to-be-saved DS