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

How do I add the CNAME record to the server? #14

Closed
eknori opened this issue Sep 12, 2017 · 3 comments
Closed

How do I add the CNAME record to the server? #14

eknori opened this issue Sep 12, 2017 · 3 comments

Comments

@eknori
Copy link

eknori commented Sep 12, 2017

I can see in the video how to get the CNAME using dig, but how do I actually ADD the record? I think, this is missing in the video.

Sorry for asking such a dumb question. I am a developer :)

@eknori
Copy link
Author

eknori commented Sep 12, 2017

Ah, I think that I got it.

  1. Register ONCE / keep credentials
  2. MANUALLY add CNAME records to config.cfg
  3. restart acme-dns
  4. update TXT
  5. on renewal goto 4

correct?

@joohoi
Copy link
Owner

joohoi commented Sep 12, 2017

Oh, no worries, there's no dumb questions, just bad documentation :)

Yes, everything else is correct, but the CNAME should be creaated manually to the actual nameserver the domain uses. So for example:

Your domain "example.com" you wish to get a certificate has nameservers hosted at provider X, and you run acme-dns on domain exampleauth.com.

After creating the acme-dns credentials using /register endpoint, you point CNAME record _acme-challenge.example.com using provider X nameservers to point to the randomly generated domain in exampleauth.com. This way you don't have to touch the X nameservers when renewing, and the automation updates the challenge token in acme-dns server that the originating domain points to using CNAME.

@joohoi
Copy link
Owner

joohoi commented Nov 12, 2017

Closing as resolved. Let me know if you still face problems and I'll reopen the issue.

@joohoi joohoi closed this as completed Nov 12, 2017
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

2 participants