-
Notifications
You must be signed in to change notification settings - Fork 65
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
challenge is failed: urn:ietf:params:acme:error:dns: DNS problem: NXDOMAIN #48
Comments
If I understand well the issue, this plugin should include an additional parameter in order to add an "extra sleep after adding the TXT record.". I will check the code to see if this doable. You could maybe also propose a PR ;-) |
If you can point me to the relevant place in code, I'll do it. But for now I saw: Line 20 in ebac646
But this is for tests. Hope you can point me and I'll work on it. |
This is where within the code we call GoDaddy to check if the TXT record exists: https://github.com/snowdrop/godaddy-webhook/blob/main/main.go#L226 |
This has become an annoying problem for the last half of the year. However, I am unsure if this is directly related to godaddy-webhook (v0.5.0) or cert-manager (v1.16.2). godaddy-webhook logs:
cert-manager logs:
It seems like the godaddy-webhook deletes the TXT record one second before the cert-manager checks it. |
In my case it worked after few hours. |
I was adding my first ingress which was x.domain.com, and the webhook went well.
few minutes later I've added x1.domain.com, and got error in the challenge says:
The TXT record seem to be created by godaddy webhook, and deleted after 750ms, once it deleted the error (found in the challenge events) the error showed up.
Can we extend the deletion time? anyone familiar with this issue?
Edit: Anyone in here now how to extend the delay? I want to try this by the answer I got: https://community.letsencrypt.org/t/challenge-failed-and-got-error-dns-problem-nxdomain-looking-up-txt/225975/4?u=david-gh
@cmoulliard maybe you can help?
The text was updated successfully, but these errors were encountered: