coolaj86/greenlock.js-ARCHIVED
3
3
Fork 0
Code Issues 6 Pull Requests 1 Releases Activity

challange is called multiple times for the same doamin #29

New Issue
Closed
opened 2019-01-07 10:18:46 +00:00 by Ghost · 2 comments
Ghost commented 2019-01-07 10:18:46 +00:00
Copy Link

Hi,
I have implemented a custom dns challenge.
But somehow, the challenge is called multiple times for the same domain.
What may be the reason for that?

Thanks

Hi, I have implemented a custom dns challenge. But somehow, the challenge is called multiple times for the same domain. What may be the reason for that? Thanks
Ghost commented 2019-01-07 14:12:51 +00:00
Author
Copy Link

i can see in the logs the message waitChallengeDelay 500 its happening in case it takes time to satisfied the dns challenge so i implement in the dns challenge handler a mechanism that query for the txt record and invoke the callback only after the TXT record returned successfully (sometimes it may take a few minutes).
What is the best practice here? what should i do if it takes time to the TXT record to be returned in a dns lookup call?

i can see in the logs the message `waitChallengeDelay 500` its happening in case it takes time to satisfied the dns challenge so i implement in the dns challenge handler a mechanism that query for the txt record and invoke the callback only after the TXT record returned successfully (sometimes it may take a few minutes). What is the best practice here? what should i do if it takes time to the TXT record to be returned in a dns lookup call?
coolaj86 commented 2019-02-05 05:09:21 +00:00
Owner
Copy Link

Sorry for the late response.

The first challenge that you'll see is actually the dry-run. The second is the real one, if the dry-run succeeds.

In your DNS-01 handlers you should do whatever is necessary to verify the DNS record before calling the callback.

  • Update via DNS provider's API
  • Verify via DNS provider's API
  • Wait some amount of time for propagation
  • Query via DNS

You'll also want to make sure that your DNS isn't set up to cache DNS misses.

I'm going to close this out, but please re-open if you still need help.

Sorry for the late response. The first challenge that you'll see is actually the dry-run. The second is the real one, if the dry-run succeeds. In your DNS-01 handlers you should do whatever is necessary to verify the DNS record _before_ calling the callback. * Update via DNS provider's API * Verify via DNS provider's API * Wait some amount of time for propagation * Query via DNS You'll also want to make sure that your DNS isn't set up to cache DNS misses. I'm going to close this out, but please re-open if you still need help.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
jshaver coolaj86
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coolaj86/greenlock.js-ARCHIVED#29
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?