Differences

This shows you the differences between two versions of the page.

--- infrastructure:services:acme_dns [2026-01-25 23:22 UTC] – [Register an Entry in ACME DNS] stb
+++ infrastructure:services:acme_dns [2026-01-25 23:44 UTC] (current) – fix urls june
@@ Line 1: / Line 1: @@
 ====== ACME DNS ======
 ---- dataentry service ----
-service-urls_urls          : http://https://acmedns.hamburg.ccc.de
+service-urls_urls          : https://acmedns.hamburg.ccc.de
 other-service-fqdns        :
 host-fqdn                  : acmedns.hosts.hamburg.ccc.de
-netbox-link_url            : http://https://netbox.hamburg.ccc.de/virtualization/virtual-machines/85/
+netbox-link_url            : https://netbox.hamburg.ccc.de/virtualization/virtual-machines/85/
 server_page                : infrastructure:servers:chaosknoten
 maintainers                : stb
@@ Line 39: / Line 39: @@
 Create a (ACME magic) CNAME record to your existing zone, pointing to the subdomain you got from the registration.
-''_acme-challenge.domainiwantcertfor.tld. CNAME a097455b-52cc-4569-90c8-7a4b97c6eba8.acmedns.hamburg.ccc.de.''
+''_acme-challenge.domainiwantcertfor.tld. CNAME 3ed25037-79f1-4a89-8934-db3e162fe2bc.auth.acmedns.hamburg.ccc.de.''
+You can request a cerificate for a wildcard DNS entry by simply creating the wildcard entry for the FQDN, and making sure the '_acme-challenge' entry aligns with it. For example, with the above entry you can add the wild card like so:
+''*.domainiwantcertfor.tld. A 192.168.0.2''
 ==== Configure ACME client ====