Hi, I’m banging my head against the wall. I’m trying to issue certificate with the dns-01 procedure. I’m on ubuntu 16.04. And this was intented to be a test. So i’m not on a production server but on my laptop. So first thing I tried this : github.com/antoiner77/letsencrypt.sh-ovh the error was : …

the thing is, In the manual hook script I do something like this after creating the record : res = Resolver() while True: try: res.query(os.environ['CERTBOT_DOMAIN']) break except: pass This is dirty bug it should work. I saw here https://certbot.eff.org/docs/using.…

[image] RemiDesgrange: So if you have any idea whatsoever thanks. Hi @RemiDesgrange , For this kind of DNS issue it's very difficult to help troubleshoot without knowing the domain name to be able to run test queries and examine the logs. Can you share the affected domain name?

Yes, fibrea.net I tried www.fibrea.net., so _acme-challenge.www.fibrea.net. (I also tried gitlab).

[image] RemiDesgrange: Yes, fibrea.net I tried www.fibrea.net ., so _acme-challenge.www.fibrea.net. (I also tried gitlab). Hi Remi, I don't see any TXT records for " www.fibrea.net " presently. Can you try to issue using the staging environment and modify the hooks so that the record created b…

You now have a TXT rec for _acme-challenge.www.fibrea.net issued by staging env.

hi @RemiDesgrange Your DNS looks good from the tests I have done [image] Andrei

It could be a matter of timing. If it takes, say, 10 seconds, or 10 minutes, for DNS changes to be reflected by all of OVH’s nameservers, and the client is having Let’s Encrypt check a moment after creating them…

Even if you do query the DNS servers, it may not be possible for you to check all of them. If they use load balancers, or a globally distributed anycast setup, you may find that some servers are up-to-date, while the Let’s Encrypt resolver hits other ones that aren’t. The only way to be sure is wit…

Let’s Encrypt always asks the authoritative nameserver for your domain - propagation is not a concern here.

@jared.m Are you absolutely sure about that [image] DNS Servers used by LetsEncrypt for Challenges Server … Andrei

Pretty sure [image] Error getting validation data on record A change Help H…

Dns01 with OVH doesn't seems to work

Issuance Tech

ahaw021 July 21, 2017, 6:48pm 11

@jared.m

Are you absolutely sure about that

Andrei

Topic		Replies	Views
DNS challenge failing: NXDOMAIN looking up TXT Issuance Tech	25	42927	August 15, 2016
DNS-01 challenge failing Help	4	7068	December 8, 2017
Error when verifying the TXT record Help	9	1999	December 11, 2020
Error DNS problem: NXDOMAIN looking up TXT - Plugin dns-ovh Help	6	1665	March 18, 2019
The Let's Encrypt HTTP challenge failed: acme error 'urn:acme:error:connection': DNS problem: SERVFAIL looking up A for domain.com	17	14314	March 15, 2016

Dns01 with OVH doesn't seems to work

Related topics