acme-dns-certbot-joohoi

Certbot client hook for acme-dns (by joohoi)

Acme-dns-certbot-joohoi Alternatives

Similar projects and alternatives to acme-dns-certbot-joohoi

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better acme-dns-certbot-joohoi alternative or higher similarity.

acme-dns-certbot-joohoi reviews and mentions

Posts with mentions or reviews of acme-dns-certbot-joohoi. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-02-21.
  • Is it okay to use letsencrypt for internet facing websites? I was going to buy a digicert cert. what's the downsides to letsencrypt vs paid public CAs?
    1 project | /r/webdev | 20 Apr 2022
    Check this out https://github.com/joohoi/acme-dns-certbot-joohoi
  • my solution to domain, certificates, ports etc (zero cost and no external server or third-party service needed)
    2 projects | /r/selfhosted | 21 Feb 2022
    we can use tool such as certbot to get certificates from let's encrypt (in traditional way). and to get one using DNS-01 challenge you can use something like acme-dns-certbot. even further the addition of TXT DNS record can be automated using a provider (in our case duckdns) specific tool/plugin for example certbot_dns_duckdns
  • Ask HN: What's your solution for SSL on internal servers?
    8 projects | news.ycombinator.com | 9 Feb 2022
    DNS alias mode:

    * https://dan.langille.org/2019/02/01/acme-domain-alias-mode/

    * https://github.com/acmesh-official/acme.sh/wiki/DNS-alias-mo...

    * https://www.eff.org/deeplinks/2018/02/technical-deep-dive-se...

    You want the name "internal.example.com". In your external DNS you create a CNAME from "_acme-challenge.internal.example.com" and point it to (e.g.) "internal.example.net" or "internal.dns-auth.example.com"

    When you request the certificate you specify the "dns-01" method. The issuer (e.g., LE) will go to the the external DNS server for the look up, see that it is a CNAME and then follow the CNAME/alias, and do the verification at the final hostname.

    So your ACME client has to do a DNS (TXT) record update, which can often be done via various APIs, e.g.:

    * https://github.com/AnalogJ/lexicon

    You can even run your own DNS server locally (in a DMZ?) if your DNS provider does not have an convenient API. There are servers written for this use case:

    * https://github.com/joohoi/acme-dns

    * https://github.com/joohoi/acme-dns-certbot-joohoi

    * https://github.com/pawitp/acme-dns-server

  • A note from our sponsor - SaaSHub
    www.saashub.com | 2 May 2024
    SaaSHub helps you find the best software and product alternatives Learn more →

Stats

Basic acme-dns-certbot-joohoi repo stats
3
204
0.0
7 months ago

joohoi/acme-dns-certbot-joohoi is an open source project licensed under MIT License which is an OSI approved license.

The primary programming language of acme-dns-certbot-joohoi is Python.


Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com