coolaj86/greenlock.js-ARCHIVED
3
3
Atdalīts 0
Kods Problēmas 6 Izmaiņu pieprasījumi 1 Laidieni Aktivitāte

challange is called multiple times for the same doamin #29

Jauna problēma
Slēgta
Ghost atvēra 2019-01-07 10:18:46 +00:00 · 2 komentāri
Ghost komentēja 2019-01-07 10:18:46 +00:00
Kopēt saiti

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 komentēja 2019-01-07 14:12:51 +00:00
Autors
Kopēt saiti

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 komentēja 2019-02-05 05:09:21 +00:00
Īpašnieks
Kopēt saiti

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.
coolaj86 slēdza šo problēmu 2019-02-05 05:09:21 +00:00
Nepieciešams pieteikties, lai pievienotos šai sarunai.
Nav norādīts atzars/tags
Atzari Tagi
Iezīmes
Nav vienumu
Nav iezīmju
Atskaites punkts
Nav vienumu
Nav atskaites punktu
Atbildīgie
Noņemt atbildīgo
jshaver coolaj86
Nav atbildīgo
2 dalībnieki
Paziņojumi
Izpildes termiņš
Izpildes termiņš nav uzstādīts.
Atkarības

Nav atkarību.

Atsaucas uz: coolaj86/greenlock.js-ARCHIVED#29
Nav sniegts apraksts.
Dzēst atzaru "%!s()"

Atzara dzēšana ir neatgriezeniska. Kaut arī izdzēstais zars neilgu laiku var turpināt pastāvēt, pirms tas tiešām tiek noņemts, to vairumā gadījumu NEVAR atsaukt. Vai turpināt?