acmesh-official / acmesh-official/acme.sh
Alle zones are retrieved -very efficient-
- Lenguaje dominante
- Shell
- Estrellas
- 47.6k
- Forks
- 5.7k
- Merge medio
- 6 d 5 h
- PR fusionados (30 d)
- 15
Descripción
We have about ~100.000 domain names / zones in powerdns and right now im testing the pdns plugin for acme.
I tested with 2 domains and it takes a long time: 6-7 minutes. In the logs i see this:
[Sun Jun 1 05:08:38 PM CEST 2025] Found domain API file: /root/.acme.sh/dnsapi/dns_pdns.sh
[Sun Jun 1 05:08:38 PM CEST 2025] Adding TXT value: 6_9PeUhNlK7zau-aaaa for domain: _acme-challenge.somedomain.nl
[Sun Jun 1 05:08:38 PM CEST 2025] Detect root zone
[Sun Jun 1 05:08:38 PM CEST 2025] GET
[Sun Jun 1 05:08:38 PM CEST 2025] url='http://pdns-myserver.someurl.nl:8081/api/v1/servers/localhost/zones'
[Sun Jun 1 05:08:38 PM CEST 2025] timeout=
[Sun Jun 1 05:08:38 PM CEST 2025] Http already initialized.
[Sun Jun 1 05:08:38 PM CEST 2025] _CURL='curl --silent --dump-header /root/.acme.sh/http.header -L -g '
The part "/api/v1/servers/localhost/zones" worries me because it gets alle the zones from our server which are about ~300.000 domain names. Can i modify the script so it only gets the zone its needs?
Many thanks!
Guía de contribución
Línea de trabajo
Check `dnsapi/dns_pdns.sh` (path shown in the log) in the zone-detection path that issues `GET /api/v1/servers/localhost/zones`. Trace how the root zone is derived from the challenge domain and whether the API flow can request only that zone. Run the dns_pdns TXT add flow against a large PowerDNS dataset and confirm the change still succeeds while avoiding a full zone-list fetch in logs.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- shell
- Área
- tooling
- Tipo de issue
- Error
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 64/100