DNS and Cert Basics

• dehydrated

  36 5,903 2.3 Shell

  letsencrypt/acme client implemented as a shell-script – just add water

  

Not meant to be comprehensive but hopefully a nudge in the right direction, I’ve found the least painful way to deal with the TLS certs is LetsEncrypt verification over DNS. There is a tool called dehydrated that implements the protocol. Then what you need is a domain, and a registrar that supports some kind of API, cause you don’t want to be renewing the certs manually every month. There is a tool called lexicon that provides programmatic access to tons of registrars.

• lexicon

  16 1,444 8.8 Python

  Manipulate DNS records on various DNS providers in a standardized way.

Not meant to be comprehensive but hopefully a nudge in the right direction, I’ve found the least painful way to deal with the TLS certs is LetsEncrypt verification over DNS. There is a tool called dehydrated that implements the protocol. Then what you need is a domain, and a registrar that supports some kind of API, cause you don’t want to be renewing the certs manually every month. There is a tool called lexicon that provides programmatic access to tons of registrars.

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• docker-dehydrated-lexicon

  1 2 0.0 Shell

  Just a container to help on requesting letsencrypt certificates with dns-01 validation

What you really need is to glue the two together. Which is actually already done for you by docker-dehydrated-lexicon as a docker container which when configured / run will run dehydrated and interface to your registrar with lexicon when necessary and then drop certificates in a directory. There are hooks so that after the cert is renewed you can copy it somewhere else. Disclaimer I have contributed to that project.

Suggest a related project