dallasgroot/Documentation
1
0
Fork 0
mirror of https://codeberg.org/Codeberg/Documentation.git synced 2026-06-16 05:13:54 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions

Add a hint about dnssec to the custom domains doc (#758)

Browse source 
I [ran](https://codeberg.org/Codeberg/Community/issues/2417) into this issue (originally reported [here](https://codeberg.org/Codeberg/Community/issues/1881)).

This is my first contribution, so I apologize in advance if I didn't follow the process properly.

Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/758
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Co-authored-by: Florian Lackner <git@lackner.work>
Co-committed-by: Florian Lackner <git@lackner.work>
This commit is contained in:
Florian Lackner 2026-03-02 02:22:25 +01:00 committed by Gusted
parent c8911bc862
commit c1e74d7e58
1 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
content/codeberg-pages/using-custom-domain.md
View file

@ -29,6 +29,9 @@ If you have a [CAA record](https://en.wikipedia.org/wiki/DNS_Certification_Autho
you must [explicitly allow Let's Encrypt in your CAA record](https://letsencrypt.org/docs/caa/).
The value of the CAA record would look like `letsencrypt.org;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/292520050;validationmethods=tls-alpn-01,http-01`.
If you're using [DNSSec](https://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions) on your custom domain, you might run into TLS certificate issues because `codeberg.page` doesn't use DNSSec at the moment.
In this case you must add `A` / `AAAA` / `TXT` records for all domains instead of `CNAME` records. You can use [this tool](https://dnssec-analyzer.verisignlabs.com) to verify your setup.
{% endadmonition %}
For custom domains, two things are required: