dallasgroot/Documentation
1
0
Fork 0
mirror of https://codeberg.org/Codeberg/Documentation.git synced 2026-08-15 14:53:29 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions

Clarify DNS provider UI pitfalls

Browse source
This commit is contained in:
crystal 2026-07-11 14:30:59 -06:00
parent f350065a74
commit 3598182daf
No known key found for this signature in database
GPG key ID: 1122054731F7CC43
1 changed files with 10 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -38,15 +38,13 @@ In this case you must add `A` / `AAAA` / `TXT` records for all domains instead o
_We assume for the following description, that you want to serve your website with and without www in front. _We assume for the following description, that you want to serve your website with and without www in front.
If you are on a subdomain already (like myproject.yourdomain.com), you can skip the `www.yourdomain.com` CNAME entry._ If you are on a subdomain already (like myproject.yourdomain.com), you can skip the `www.yourdomain.com` CNAME entry._
{% admonition "Warning" %} {% admonition "warning" "DNS provider interface pitfalls" %}
When setting up DNS records with many registrars, any domain added to the `Domain` or `Host` option is automatically There is no widely accepted standard for displaying DNS record hosts in a user interface. As a result, the specific details of what this is supposed to look like may vary drastically depending on your DNS provider.
appended onto the domain the records are being made for.
For example, if your domain is `example.com`, entering `www` will mean the record refers to `www.example.com`. For many providers, your domain is implicitly appended to the value of the `Host` option, so you must only supply the part that comes before your apex domain if you wish to use a subdomain (i.e. use `www` instead of `www.example.org`). To assign records to the apex domain on such providers, you typically must supply a single `@` or leave the `Host` field blank.
Therefore, in this guide, you may need to replace references to just your domain name (e.g. `example.com`) with `@` and Failure to observe this quirk will cause your records to be incorrectly served for redundant subdomains, such as `www.example.org.example.org`
`anything.example.com` (i.e. any subdomain) with just `anything`.
{% endadmonition %} {% endadmonition %}
@ -76,6 +74,12 @@ DNSSEC has now been enabled for `codeberg.page`, try using a CNAME record if you
{% endadmonition %} {% endadmonition %}
{% admonition "question" "DNS provider interface pitfalls" %}
The target of a properly formed CNAME record should always end with a `.`, however this may not be meaningfully represented in some providers' user interfaces. If your provider throws an error when setting up a record like this, try omitting the trailing `.`
{% endadmonition %}
{% admonition "Warning" %} {% admonition "Warning" %}
With a CNAME record, everything on this subdomain is delegated to `codeberg.page`, which means you cannot setup other types of DNS records for other services on the same subdomain. With a CNAME record, everything on this subdomain is delegated to `codeberg.page`, which means you cannot setup other types of DNS records for other services on the same subdomain.