{"id":37148480,"url":"https://github.com/liquidweb/acme-dns","last_synced_at":"2026-01-14T17:32:13.883Z","repository":{"id":57586054,"uuid":"142599024","full_name":"liquidweb/acme-dns","owner":"liquidweb","description":"Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.","archived":false,"fork":true,"pushed_at":"2018-08-01T18:28:17.000Z","size":17022,"stargazers_count":1,"open_issues_count":0,"forks_count":0,"subscribers_count":4,"default_branch":"master","last_synced_at":"2025-10-20T17:50:26.384Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":"Go","has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":"joohoi/acme-dns","license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/liquidweb.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2018-07-27T16:15:47.000Z","updated_at":"2019-11-22T20:22:29.000Z","dependencies_parsed_at":null,"dependency_job_id":null,"html_url":"https://github.com/liquidweb/acme-dns","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/liquidweb/acme-dns","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/liquidweb%2Facme-dns","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/liquidweb%2Facme-dns/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/liquidweb%2Facme-dns/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/liquidweb%2Facme-dns/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/liquidweb","download_url":"https://codeload.github.com/liquidweb/acme-dns/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/liquidweb%2Facme-dns/sbom","scorecard":{"id":592176,"data":{"date":"2025-08-11","repo":{"name":"github.com/liquidweb/acme-dns","commit":"8aa869b2f8ee4814910fcbcc960c1614981feb6d"},"scorecard":{"version":"v5.2.1-40-gf6ed084d","commit":"f6ed084d17c9236477efd66e5b258b9d4cc7b389"},"score":2.7,"checks":[{"name":"Packaging","score":-1,"reason":"packaging workflow not detected","details":["Warn: no GitHub/GitLab publishing workflow detected."],"documentation":{"short":"Determines if the project is published as a package that others can easily download, install, easily update, and uninstall.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#packaging"}},{"name":"Dangerous-Workflow","score":-1,"reason":"no workflows found","details":null,"documentation":{"short":"Determines if the project's GitHub Action workflows avoid dangerous patterns.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#dangerous-workflow"}},{"name":"Token-Permissions","score":-1,"reason":"No tokens found","details":null,"documentation":{"short":"Determines if the project's workflows follow the principle of least privilege.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#token-permissions"}},{"name":"Code-Review","score":0,"reason":"Found 0/30 approved changesets -- score normalized to 0","details":null,"documentation":{"short":"Determines if the project requires human code review before pull requests (aka merge requests) are merged.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#code-review"}},{"name":"Maintained","score":0,"reason":"0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0","details":null,"documentation":{"short":"Determines if the project is \"actively maintained\".","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#maintained"}},{"name":"CII-Best-Practices","score":0,"reason":"no effort to earn an OpenSSF best practices badge detected","details":null,"documentation":{"short":"Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#cii-best-practices"}},{"name":"SAST","score":0,"reason":"no SAST tool detected","details":["Warn: no pull requests merged into dev branch"],"documentation":{"short":"Determines if the project uses static code analysis.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#sast"}},{"name":"Security-Policy","score":0,"reason":"security policy file not detected","details":["Warn: no security policy file detected","Warn: no security file to analyze","Warn: no security file to analyze","Warn: no security file to analyze"],"documentation":{"short":"Determines if the project has published a security policy.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#security-policy"}},{"name":"Binary-Artifacts","score":10,"reason":"no binaries found in the repo","details":null,"documentation":{"short":"Determines if the project has generated executable (binary) artifacts in the source repository.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#binary-artifacts"}},{"name":"Fuzzing","score":0,"reason":"project is not fuzzed","details":["Warn: no fuzzer integrations found"],"documentation":{"short":"Determines if the project uses fuzzing.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#fuzzing"}},{"name":"License","score":10,"reason":"license file detected","details":["Info: project has a license file: LICENSE:0","Info: FSF or OSI recognized license: MIT License: LICENSE:0"],"documentation":{"short":"Determines if the project has defined a license.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#license"}},{"name":"Signed-Releases","score":-1,"reason":"no releases found","details":null,"documentation":{"short":"Determines if the project cryptographically signs release artifacts.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#signed-releases"}},{"name":"Branch-Protection","score":0,"reason":"branch protection not enabled on development/release branches","details":["Warn: branch protection not enabled for branch 'master'"],"documentation":{"short":"Determines if the default and release branches are protected with GitHub's branch protection settings.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#branch-protection"}},{"name":"Pinned-Dependencies","score":0,"reason":"dependency not pinned by hash detected -- score normalized to 0","details":["Warn: containerImage not pinned by hash: Dockerfile:1","Warn: containerImage not pinned by hash: Dockerfile:10: pin your Docker image by updating alpine:latest to alpine:latest@sha256:4bcff63911fcb4448bd4fdacec207030997caf25e9bea4045fa6c8c44de311d1","Warn: goCommand not pinned by hash: Dockerfile:6","Warn: goCommand not pinned by hash: vendor/github.com/lib/pq/.travis.sh:82","Warn: goCommand not pinned by hash: vendor/github.com/lib/pq/.travis.sh:84","Warn: goCommand not pinned by hash: vendor/github.com/lib/pq/.travis.sh:95","Warn: goCommand not pinned by hash: vendor/github.com/stretchr/testify/.travis.gogenerate.sh:7","Info:   0 out of   2 containerImage dependencies pinned","Info:   0 out of   5 goCommand dependencies pinned"],"documentation":{"short":"Determines if the project has declared and pinned the dependencies of its build process.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#pinned-dependencies"}},{"name":"Vulnerabilities","score":9,"reason":"1 existing vulnerabilities detected","details":["Warn: Project is vulnerable to: CVE-2021-28484"],"documentation":{"short":"Determines if the project has open, known unfixed vulnerabilities.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#vulnerabilities"}}]},"last_synced_at":"2025-08-20T22:13:57.765Z","repository_id":57586054,"created_at":"2025-08-20T22:13:57.766Z","updated_at":"2025-08-20T22:13:57.766Z"},"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28428301,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-14T16:38:47.836Z","status":"ssl_error","status_checked_at":"2026-01-14T16:34:59.695Z","response_time":107,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.5:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2026-01-14T17:32:13.224Z","updated_at":"2026-01-14T17:32:13.870Z","avatar_url":"https://github.com/liquidweb.png","language":"Go","funding_links":[],"categories":[],"sub_categories":[],"readme":"[![Build Status](https://travis-ci.org/joohoi/acme-dns.svg?branch=master)](https://travis-ci.org/joohoi/acme-dns) [![Coverage Status](https://coveralls.io/repos/github/joohoi/acme-dns/badge.svg?branch=master)](https://coveralls.io/github/joohoi/acme-dns?branch=master) [![Go Report Card](https://goreportcard.com/badge/github.com/joohoi/acme-dns)](https://goreportcard.com/report/github.com/joohoi/acme-dns)\n# acme-dns\n\nA simplified DNS server with a RESTful HTTP API to provide a simple way to automate ACME DNS challenges.\n\n## Why?\n\nMany DNS servers do not provide an API to enable automation for the ACME DNS challenges. Those which do, give the keys way too much power.\nLeaving the keys laying around your random boxes is too often a requirement to have a meaningful process automation.\n\nAcme-dns provides a simple API exclusively for TXT record updates and should be used with ACME magic \"\\_acme-challenge\" - subdomain CNAME records. This way, in the unfortunate exposure of API keys, the effects are limited to the subdomain TXT record in question.\n\nSo basically it boils down to **accessibility** and **security**.\n\n## Features\n- Simplified DNS server, serving your ACME DNS challenges (TXT)\n- Custom records (have your required A, AAAA, NS, etc. records served)\n- HTTP API automatically acquires and uses Let's Encrypt TLS certificate\n- Limit /update API endpoint access to specific CIDR mask(s), defined in the /register request\n- Supports SQLite \u0026 PostgreSQL as DB backends\n- Rolling update of two TXT records to be able to answer to challenges for certificates that have both names: `yourdomain.tld` and `*.yourdomain.tld`, as both of the challenges point to the same subdomain.\n- Simple deployment (it's Go after all)\n\n## Usage\n\nA Certbot authentication hook for acme-dns is available at: [https://github.com/joohoi/acme-dns-certbot](https://github.com/joohoi/acme-dns-certbot).\n\n[![asciicast](https://asciinema.org/a/94903.png)](https://asciinema.org/a/94903)\n\nUsing acme-dns is a three-step process (provided you already have the self-hosted server set up):\n\n- Get credentials and unique subdomain (simple POST request to eg. https://auth.acme-dns.io/register)\n- Create a (ACME magic) CNAME record to your existing zone, pointing to the subdomain you got from the registration. (eg. `_acme-challenge.domainiwantcertfor.tld. CNAME a097455b-52cc-4569-90c8-7a4b97c6eba8.auth.example.org` )\n- Use your credentials to POST new DNS challenge values to an acme-dns server for the CA to validate from.\n- Crontab and forget.\n\n## API\n\n### Register endpoint\n\nThe method returns a new unique subdomain and credentials needed to update your record.\nFulldomain is where you can point your own `_acme-challenge` subdomain CNAME record to.\nWith the credentials, you can update the TXT response in the service to match the challenge token, later referred as \\_\\_\\_validation\\_token\\_received\\_from\\_the\\_ca\\_\\_\\_, given out by the Certificate Authority.\n\n**Optional:**: You can POST JSON data to limit the `/update` requests to predefined source networks using CIDR notation.\n\n```POST /register```\n\n#### OPTIONAL Example input\n```json\n{\n    \"allowfrom\": [\n        \"192.168.100.1/24\",\n        \"1.2.3.4/32\",\n        \"2002:c0a8:2a00::0/40\"\n    ]\n}\n```\n\n\n```Status: 201 Created```\n```json\n{\n    \"allowfrom\": [\n        \"192.168.100.1/24\",\n        \"1.2.3.4/32\",\n        \"2002:c0a8:2a00::0/40\"\n    ],\n    \"fulldomain\": \"8e5700ea-a4bf-41c7-8a77-e990661dcc6a.auth.acme-dns.io\",\n    \"password\": \"htB9mR9DYgcu9bX_afHF62erXaH2TS7bg9KW3F7Z\",\n    \"subdomain\": \"8e5700ea-a4bf-41c7-8a77-e990661dcc6a\",\n    \"username\": \"c36f50e8-4632-44f0-83fe-e070fef28a10\"\n}\n```\n\n### Update endpoint\n\nThe method allows you to update the TXT answer contents of your unique subdomain. Usually carried automatically by automated ACME client.\n\n```POST /update```\n\n#### Required headers\n| Header name   | Description                                | Example                                               |\n| ------------- |--------------------------------------------|-------------------------------------------------------|\n| X-Api-User    | UUIDv4 username received from registration | `X-Api-User: c36f50e8-4632-44f0-83fe-e070fef28a10`    |\n| X-Api-Key     | Password received from registration        | `X-Api-Key: htB9mR9DYgcu9bX_afHF62erXaH2TS7bg9KW3F7Z` |\n\n#### Example input\n```json\n{\n    \"subdomain\": \"8e5700ea-a4bf-41c7-8a77-e990661dcc6a\",\n    \"txt\": \"___validation_token_received_from_the_ca___\"\n}\n```\n\n#### Response\n\n```Status: 200 OK```\n```json\n{\n    \"txt\": \"___validation_token_received_from_the_ca___\"\n}\n```\n\n## Self-hosted\n\nYou are encouraged to run your own acme-dns instance, because you are effectively authorizing the acme-dns server to act on your behalf in providing the answer to the challenging CA, making the instance able to request (and get issued) a TLS certificate for the domain that has CNAME pointing to it.\n\nSee the INSTALL section for information on how to do this.\n\n\n## Installation\n\n1) Install [Go 1.9 or newer](https://golang.org/doc/install).\n\n2) Install acme-dns: `go get github.com/joohoi/acme-dns/...`. This will install acme-dns to `~/go/bin/acme-dns`.\n\n3) Edit config.cfg to suit your needs (see [configuration](#configuration)). `acme-dns` will read the configuration file from `/etc/acme-dns/config.cfg` or `./config.cfg`.\n\n4) If your system has systemd, you can optionally install acme-dns as a service so that it will start on boot and be tracked by systemd. This also allows us to add the `CAP_NET_BIND_SERVICE` capability so that acme-dns can be run by a user other than root.\n\n    1) Make sure that you have moved the configuration file to `/etc/acme-dns/config.cfg` so that acme-dns can access it globally.\n\n    2) Move the acme-dns executable from `~/go/bin/acme-dns` to `/usr/local/bin/acme-dns` (Any location will work, just be sure to change `acme-dns.service` to match).\n\n    3) Create a minimal acme-dns user: `sudo adduser --system --gecos \"acme-dns Service\" --disabled-password --group --home /var/lib/acme-dns acme-dns`.\n\n    4) Move the systemd service unit from `acme-dns.service` to `/etc/systemd/system/acme-dns.service`.\n\n    5) Reload systemd units: `sudo systemctl daemon-reload`.\n\n    6) Enable acme-dns on boot: `sudo systemctl enable acme-dns.service`.\n\n    7) Run acme-dns: `sudo systemctl start acme-dns.service`.\n\n5) If you did not install the systemd service, run `acme-dns`. Please note that acme-dns needs to open a privileged port (53, domain), so it needs to be run with elevated privileges.\n\n### Using Docker\n\n1) Pull the latest acme-dns Docker image: `docker pull joohoi/acme-dns`.\n\n2) Create directories: `config` for the configuration file, and `data` for the sqlite3 database.\n\n3) Copy [configuration template](https://raw.githubusercontent.com/joohoi/acme-dns/master/config.cfg) to `config/config.cfg`.\n\n4) Modify the `config.cfg` to suit your needs.\n\n5) Run Docker, this example expects that you have `port = \"80\"` in your `config.cfg`:\n```\ndocker run --rm --name acmedns                 \\\n -p 53:53                                      \\\n -p 80:80                                      \\\n -v /path/to/your/config:/etc/acme-dns:ro      \\\n -v /path/to/your/data:/var/lib/acme-dns       \\\n -d joohoi/acme-dns\n```\n\n### Docker Compose\n\n1) Create directories: `config` for the configuration file, and `data` for the sqlite3 database.\n\n2) Copy [configuration template](https://raw.githubusercontent.com/joohoi/acme-dns/master/config.cfg) to `config/config.cfg`.\n\n3) Copy [docker-compose.yml from the project](https://raw.githubusercontent.com/joohoi/acme-dns/master/docker-compose.yml), or create your own.\n\n4) Edit the `config/config.cfg` and `docker-compose.yml` to suit your needs, and run `docker-compose up -d`.\n\n## DNS Records\n\nNote: In this documentation:\n- `example.com` is your domain name\n- `auth.example.com` is the subdomain you want to use for acme-dns\n- `198.51.100.1` is the **public** IP address of the system running acme-dns  \n\nThese values should be changed based on your environment.\n\nYou will need to add some DNS records on your domain's regular DNS server:\n- `NS` record for `auth.example.com` pointing to `ns.auth.example.com`\n- `A` record for `ns.auth.example.com` pointing to `198.51.100.1`\n- If using IPv6, an `AAAA` record pointing to the IPv6 address.\n- Each domain you will be authenticating will need a `_acme-challenge` `CNAME` subdomain added. The [client](README.md#clients) you use will explain how to do this.\n\n## Testing It Out\n\nYou may want to test that acme-dns is working before using it for real queries.\n\n1) Confirm that DNS lookups for the acme-dns subdomain works as expected: `dig auth.example.com`.\n\n2) Call the `/register` API endpoint to register a test domain:\n```\n$ curl -X POST http://auth.example.com/register\n{\"username\":\"eabcdb41-d89f-4580-826f-3e62e9755ef2\",\"password\":\"pbAXVjlIOE01xbut7YnAbkhMQIkcwoHO0ek2j4Q0\",\"fulldomain\":\"d420c923-bbd7-4056-ab64-c3ca54c9b3cf.auth.example.com\",\"subdomain\":\"d420c923-bbd7-4056-ab64-c3ca54c9b3cf\",\"allowfrom\":[]}\n```\n\n3) Call the `/update` API endpoint to set a test TXT record. Pass the `username`, `password` and `subdomain` received from the `register` call performed above:\n```\n$ curl -X POST \\\n  -H \"X-Api-User: eabcdb41-d89f-4580-826f-3e62e9755ef2\" \\\n  -H \"X-Api-Key: pbAXVjlIOE01xbut7YnAbkhMQIkcwoHO0ek2j4Q0\" \\\n  -d '{\"subdomain\": \"d420c923-bbd7-4056-ab64-c3ca54c9b3cf\", \"txt\": \"___validation_token_received_from_the_ca___\"}' \\\n  http://auth.example.com/update\n```\n\nNote: The `txt` field must be exactly 43 characters long, otherwise acme-dns will reject it\n\n4) Perform a DNS lookup to the test subdomain to confirm that everything is working properly:\n```\n$ dig @ns.auth.example.com d420c923-bbd7-4056-ab64-c3ca54c9b3cf.auth.example.com\n```\n\n## Configuration\n\n```bash\n[general]\n# dns interface\nlisten = \":53\"\n# protocol, \"udp\", \"udp4\", \"udp6\" or \"tcp\", \"tcp4\", \"tcp6\"\nprotocol = \"udp\"\n# domain name to serve the requests off of\ndomain = \"auth.example.org\"\n# zone name server\nnsname = \"ns1.auth.example.org\"\n# admin email address, where @ is substituted with .\nnsadmin = \"admin.example.org\"\n# predefined records served in addition to the TXT\nrecords = [\n    # default A\n    \"auth.example.org. A 192.168.1.100\",\n    # A\n    \"ns1.auth.example.org. A 192.168.1.100\",\n    \"ns2.auth.example.org. A 192.168.1.100\",\n    # NS\n    \"auth.example.org. NS ns1.auth.example.org.\",\n    \"auth.example.org. NS ns2.auth.example.org.\",\n]\n# debug messages from CORS etc\ndebug = false\n\n[database]\n# Database engine to use, sqlite3 or postgres\nengine = \"sqlite3\"\n# Connection string, filename for sqlite3 and postgres://$username:$password@$host/$db_name for postgres\nconnection = \"acme-dns.db\"\n# connection = \"postgres://user:password@localhost/acmedns_db\"\n\n[api]\n# domain name to listen requests for, mandatory if using tls = \"letsencrypt\"\napi_domain = \"\"\n# disable registration endpoint\ndisable_registration = false\n# autocert HTTP port, eg. 80 for answering Let's Encrypt HTTP-01 challenges. Mandatory if using tls = \"letsencrypt\".\nautocert_port = \"80\"\n# listen ip, default \"\" listens on all interfaces/addresses\nip = \"127.0.0.1\"\n# listen port, eg. 443 for default HTTPS\nport = \"8080\"\n# possible values: \"letsencrypt\", \"cert\", \"none\"\ntls = \"none\"\n# only used if tls = \"cert\"\ntls_cert_privkey = \"/etc/tls/example.org/privkey.pem\"\ntls_cert_fullchain = \"/etc/tls/example.org/fullchain.pem\"\n# only used if tls = \"letsencrypt\"\nacme_cache_dir = \"api-certs\"\n# CORS AllowOrigins, wildcards can be used\ncorsorigins = [\n    \"*\"\n]\n\n[logconfig]\n# logging level: \"error\", \"warning\", \"info\" or \"debug\"\nloglevel = \"debug\"\n# possible values: stdout, TODO file \u0026 integrations\nlogtype = \"stdout\"\n# file path for logfile TODO\n# logfile = \"./acme-dns.log\"\n# format, either \"json\" or \"text\"\nlogformat = \"text\"\n# use HTTP header to get the client ip\nuse_header = false\n# header name to pull the ip address / list of ip addresses from\nheader_name = \"X-Forwarded-For\"\n```\n\n## Clients\n\n- acme.sh: [https://github.com/Neilpang/acme.sh](https://github.com/Neilpang/acme.sh)\n- Lego: [https://github.com/xenolf/lego](https://github.com/xenolf/lego)\n- Posh-ACME: [https://github.com/rmbolger/Posh-ACME](https://github.com/rmbolger/Posh-ACME)\n- Sewer: [https://github.com/komuw/sewer](https://github.com/komuw/sewer)\n\n### Authentication hooks\n\n- Certbot authentication hook in Python:  [https://github.com/joohoi/acme-dns-certbot-joohoi](https://github.com/joohoi/acme-dns-certbot-joohoi)\n- Certbot authentication hook in Go: [https://github.com/koesie10/acme-dns-certbot-hook](https://github.com/koesie10/acme-dns-certbot-hook)\n\n### Libraries\n\n- Generic client library in Python ([PyPI](https://pypi.python.org/pypi/pyacmedns/)): [https://github.com/joohoi/pyacmedns](https://github.com/joohoi/pyacmedns)\n- Generic client library in Go: [https://github.com/cpu/goacmedns](https://github.com/cpu/goacmedns)\n\n\n## Changelog\n- v0.4 Clear error messages for bad TXT record content, proper handling of static CNAME records, fixed IP address parsing from the request, added option to disable registration endpoint in the configuration.\n- v0.3.2 Dockerfile was fixed for users using autocert feature\n- v0.3.1 Added goreleaser for distributing binary builds of the releases\n- v0.3 Changed autocert to use HTTP-01 challenges, as TLS-SNI is disabled by Let's Encrypt\n- v0.2 Now powered by httprouter, support wildcard certificates, Docker images\n- v0.1 Initial release\n\n## TODO\n\n- Logging to a file\n- DNSSEC\n- Want to see something implemented, make a feature request!\n\n## Contributing\n\nacme-dns is open for contributions.\nIf you have an idea for improvement, please open an new issue or feel free to write a PR!\n\n## License\n\nacme-dns is released under the [MIT License](http://www.opensource.org/licenses/MIT).\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fliquidweb%2Facme-dns","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fliquidweb%2Facme-dns","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fliquidweb%2Facme-dns/lists"}