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

Csync crashes on invalid dns records #2024

Closed
vohmar opened this issue Jun 8, 2021 · 7 comments · Fixed by #2025
Closed

Csync crashes on invalid dns records #2024

vohmar opened this issue Jun 8, 2021 · 7 comments · Fixed by #2025
Assignees
Labels

Comments

@vohmar
Copy link
Contributor

vohmar commented Jun 8, 2021

the registry update process crashes when csync process of monitoring cdnskey records, updating registry and validating the dns record.

@vohmar vohmar added the bug label Jun 8, 2021
@ratM1n
Copy link

ratM1n commented Jun 8, 2021

Problem is with "CsyncJob" task. When targeted authoritative DNS is not reachable for some reason, the script will crash. Log from such a crash : https://gist.github.com/ratM1n/3a7bfb657330e1141e736f951b8fb159

@yulgolem
Copy link
Contributor

yulgolem commented Jun 8, 2021

What behaviour we are waiting for?
I could add the timeout processing, but what could we do in that case? Exponential retries?

@ratM1n
Copy link

ratM1n commented Jun 8, 2021

We should skip the current record and throw some error to stdoud, stating domain in question and dns which wasn't reachable.
For example:
[time] <domain name> <dns server's name and|or ip> <reason for error>

@ratM1n
Copy link

ratM1n commented Jun 9, 2021

can you please check what is done in case then log output is as: I, [2021-06-09T09:16:45.987428 #7353] INFO -- : CsyncJob: : Reseting state. Reason: Nameserver(s) not reachable / invalid data (secure-empty)

@yulgolem
Copy link
Contributor

yulgolem commented Jun 9, 2021

Well, what's it, the empty record is unqualified for monitoring.
String generated as per

@logger.info "CsyncJob: #{domain}: Reseting state. Reason: " +
                 unqualification_reason(ns_ok, key_ok, result_types)

And I see no info about domain in the log message.

@ratM1n
Copy link

ratM1n commented Jun 9, 2021

Found one more problem - whois is not updated if dnssec is removed from domain.

@ratM1n
Copy link

ratM1n commented Jun 9, 2021

OK, whois updated worked in staging.

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

Successfully merging a pull request may close this issue.

3 participants