-
Hi, as follow up to #2259 , here the next step: Now Gandi timeout set at 120s, it seems to go forward, but still fails while checking propagation, it seems still related to a timeout linked to Gandi again. The gandi dns record reference (here
I even set the acme resolver to a Gandi DNS, no luck. Any advise? Thank you. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
During the propagation, lego checks the TXT record propagation to name servers (NS) of your domain. So the problem is with Gandi NSs, either one (at least) is not working or one (at least) is in difficulties (and so very slow). |
Beta Was this translation helpful? Give feedback.
-
Damn, you never sleep! Thank you again @ldez , it looks like Gandi QoS is awnful for a whole year at least. I mark this as answer, and I’ll give up on Gandi as DNS challenge resolver for now. Thank you again for your impressives prompt responses. |
Beta Was this translation helpful? Give feedback.
During the propagation, lego checks the TXT record propagation to name servers (NS) of your domain.
The timeout happens because one (at least) of the NS (
ns-38-c.gandi.net.
) didn't answer in time at a DNS call to get the TXT records.So the problem is with Gandi NSs, either one (at least) is not working or one (at least) is in difficulties (and so very slow).