Skip to content
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

DNS problem: NXDOMAIN looking up TXT for _acme-challenge. #595

Closed
JOduMonT opened this issue Sep 18, 2018 · 2 comments
Closed

DNS problem: NXDOMAIN looking up TXT for _acme-challenge. #595

JOduMonT opened this issue Sep 18, 2018 · 2 comments

Comments

@JOduMonT
Copy link

Hi;

I know it's not related to dehydrated and/or the hooks but I miss understood something;

do I have to create the TXT _acme-challenge. ?
if yes where I found the VALUE
may I have a concrete example ?

Regards!

Jonathan

@txr13
Copy link

txr13 commented Sep 18, 2018

You need to create a TXT record of the form:

_acme-challenge.certificatedomain.tld.

For example, if my certificate name was “certify-me.example.org” my TXT record would be “_acme-challenge.certify-me.example.org.” The value of that record will be given by the ACME CA server.

@lukas2511
Copy link
Member

You (or ideally a script) have to create a _acme-challenge.yourdomain.tld TXT-record. The value for that will be generated by the Let's Encrypt server and dehydrated will call a hook-script with those values so they can be deployed. You should have a look at the example hook script which has an example deployment using nsupdate, or you could have a look at the project wiki where you can find a big list of user-provided hook-scripts for a ton of DNS providers / APIs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants