From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 055A27262C for ; Mon, 12 Apr 2021 21:29:19 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id DBC9D22B5F for ; Mon, 12 Apr 2021 21:28:48 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 00EA522B46 for ; Mon, 12 Apr 2021 21:28:47 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id B961A45A5E for ; Mon, 12 Apr 2021 21:28:46 +0200 (CEST) From: Stoiko Ivanov To: pmg-devel@lists.proxmox.com Date: Mon, 12 Apr 2021 21:28:33 +0200 Message-Id: <20210412192833.21988-4-s.ivanov@proxmox.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20210412192833.21988-1-s.ivanov@proxmox.com> References: <20210412192833.21988-1-s.ivanov@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.059 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pmg-devel] [PATCH pmg-docs v2 1/1] certs: add wildcard certificate support X-BeenThere: pmg-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Mail Gateway development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Apr 2021 19:29:19 -0000 Signed-off-by: Stoiko Ivanov --- pmg-ssl-certificate.adoc | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/pmg-ssl-certificate.adoc b/pmg-ssl-certificate.adoc index 6cd44b1..24e8d71 100644 --- a/pmg-ssl-certificate.adoc +++ b/pmg-ssl-certificate.adoc @@ -187,6 +187,23 @@ and set the `alias` property in the {pmg} node configuration file `/etc/pmg/node.conf` to `domain2.example` to allow the DNS server of `domain2.example` to validate all challenges for `domain1.example`. +[[sysadmin_certs_acme_dns_wildcard]] +Wildcard Certificates +^^^^^^^^^^^^^^^^^^^^^ +You can create a certificate for a 'wildcard DNS name' as described in +https://community.letsencrypt.org/t/acme-v2-production-environment-wildcards/55578[ACME v2 Production Environment & Wildcards]. + +Wildcard DNS names start with a `*.` prefix and are considered valid for all +(one-level) subdomain names of the verified domain. So a certificate for +`*.domain.example` is valid for example for `foo.domain.example` and +`bar.domain.example`. + +Verification for wildcard DNS names only works with the `dns-01` validation +method. + +You need to configure both the base domain (`domain.example`) as well as the +wildcard equivalent (`*.domain.example`) under `Certificates` with a DNS plugin. + Combination of Plugins ^^^^^^^^^^^^^^^^^^^^^^ -- 2.20.1