[GH-ISSUE #14] How do I add the CNAME record to the server? #1

New issue

Closed

opened 2026-03-13 15:18:38 +03:00 by kerem · 3 comments

kerem commented

2026-03-13 15:18:38 +03:00

Owner

Originally created by @eknori on GitHub (Sep 12, 2017).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/14

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 :)

Originally created by @eknori on GitHub (Sep 12, 2017). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/14 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 :)

kerem closed this issue

2026-03-13 15:18:43 +03:00

kerem commented

2026-03-13 15:18:49 +03:00

Author

Owner

@eknori commented on GitHub (Sep 12, 2017):

Ah, I think that I got it.

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

correct?

@eknori commented on GitHub (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?

kerem commented

2026-03-13 15:18:54 +03:00

Author

Owner

@joohoi commented on GitHub (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 commented on GitHub (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.

kerem commented

2026-03-13 15:18:59 +03:00

Author

Owner

@joohoi commented on GitHub (Nov 12, 2017):

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

@joohoi commented on GitHub (Nov 12, 2017): Closing as resolved. Let me know if you still face problems and I'll reopen the issue.

kerem referenced this issue

2026-03-13 15:19:14 +03:00

[GH-ISSUE #13] No JSON object could be decoded #3

kerem referenced this issue

2026-03-13 15:19:25 +03:00

[GH-ISSUE #13] No JSON object could be decoded #3

kerem referenced this issue

2026-03-13 15:34:01 +03:00

[GH-ISSUE #156] ssl3_read_bytes:tlsv1 alert internal error #56

kerem referenced this issue

2026-03-13 16:12:46 +03:00

[PR #1] [CLOSED] Break intentionally #232