# dnsrobocert mit Homebrew installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für dnsrobocert in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:dnsrobocert
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install dnsrobocert
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:dnsrobocert
- **Paketmanager:** Homebrew
- **Version:** 3.27.0
- **Quellzusammenfassung:** Manage Let's Encrypt SSL certificates based on DNS challenges
- **Homepage:** <https://dnsrobocert.readthedocs.io/en/latest/>
- **Repository:** <https://github.com/adferrand/dnsrobocert>
- **Zuletzt aktualisiert:** 2026-06-20T10:48:00Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- dnsrobocert (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 3.27.0
## Projektgeschichte und Nutzung

DNSroboCert is a certificate automation tool for Let's Encrypt DNS-01 challenges. Its niche is coordinating ACME issuance, DNS provider credentials, renewal, and post-renewal hooks in one YAML-driven service.

### Projektgeschichte

The GitHub repository was created in June 2017, and the first GitHub release, 1.0.0, followed later that month. The official documentation describes the design as orchestration of Certbot for certificate issuance and Lexicon for standardized DNS provider updates.

The project grew around the operational gap left by HTTP/TLS challenge tools: private services, non-web services, wildcard certificates, and deployments where opening an inbound web challenge is not practical. Its documentation emphasizes Docker support, dynamic reload of configuration, regular renewal, hooks, and DNS alias mode.

### Adoptionsgeschichte

DNSroboCert is packaged for Homebrew, but its official user guide presents pipx and Docker as the main installation paths. That fits its audience: self-hosters and operators who want long-running certificate automation rather than a one-shot ACME client invocation.

### Wie es verwendet wird

Users maintain a central YAML file, typically /etc/dnsrobocert/config.yml, with acme, profiles, and certificates sections. Profiles hold DNS provider credentials for Lexicon, certificates reference those profiles, and the service validates the file before issuing or renewing certificates.

### Warum Paket-Nerds sich dafür interessieren

DNSroboCert is interesting to package maintainers because it wraps several moving parts that usually leak into local scripts: Certbot, Lexicon provider plugins, provider credentials, renewal cadence, Docker volumes, and certificate propagation hooks. Its package surface is small, but its runtime configuration is security-sensitive.

### Zeitleiste

- 2017: GitHub repository created.
- 2017: First GitHub release, 1.0.0, published.
- 2020: Documentation examples use the 3.0.0 installation flow and container paths.
- 2026: v3.27.0 release published and Read the Docs displays DNSroboCert 3.27.0 documentation.

### Related projects

- Certbot is the underlying ACME client named by the docs. Lexicon provides the DNS provider API layer. The docs compare DNSroboCert's use case with reverse-proxy automation such as Traefik and nginx-proxy companion, and mention acme.sh DNS alias mode as related DNS challenge practice.

### Quellen

- <https://dnsrobocert.readthedocs.io/en/latest/>
- <https://dnsrobocert.readthedocs.io/en/latest/user_guide.html>
- <https://dnsrobocert.readthedocs.io/en/latest/configuration_reference.html>
- <https://api.github.com/repos/adferrand/dnsrobocert>
- <https://api.github.com/repos/adferrand/dnsrobocert/releases?per_page=100>
- <https://formulae.brew.sh/formula/dnsrobocert>


## Sicherheitshinweise

Für dnsrobocert wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.



## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: /etc/dnsrobocert/config.yml

## Credential files

- Unix: /etc/dnsrobocert/config.yml

## Combined YAML source

View the package source record on GitHub. [combined/dnsrobocert.yml](https://github.com/mxcl/pkgdb/blob/main/combined/dnsrobocert.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph