Forum Discussion
TimRiker
Cirrocumulus
Nov 25, 2025ACME DNS RFC-2136 Let's Encrypt certs
I've been pushing on certbot to handle CNAME entries when ordering certs, and finally given up.
- https://github.com/certbot/certbot/issues/6787
- https://github.com/certbot/certbot/pull/9970
- https://github.com/certbot/certbot/pull/7244
This repo contains scripts that:
- Create an ACME account with Let's Encrypt
- use TSIG credentials to talk to bind (RFC-2136)
- create TXT record in correct zone by following CNAME and SOA entries if present
- downloads certs
- installs certs on one or more F5s.
The F5 credentials requires Administrator rights as Certificate Manager can't upload files.
CNAME records are recommended to a zone with minimal or no replication and a low TTL. ie:
- _acme-challenge.example.com CNAME example.com._tls.example.com
- _acme-challenge.example.net CNAME example.net._tls.example.com
- _tls.example.com would have one name server and 30 second TTL or so
- a TSIG key would be created that only needs update access to _tls.example.com
Comments welcome. JRahm I'm looking at you. 😎
More info:
1 Reply
- TimRiker
Cirrocumulus
Posted some bug fixes and updated the documentation.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects
