update Codeberg Pages IP addresses (#556)

Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/556
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Co-authored-by: crystal <crystal@noreply.codeberg.org>
Co-committed-by: crystal <crystal@noreply.codeberg.org>
This commit is contained in:
crystal 2025-04-23 13:43:54 +00:00 committed by Gusted
parent 5a242e44fb
commit 9a55f7bf8b

View file

@ -131,8 +131,8 @@ In the end it should look like this:
If your service provider does not support `ALIAS records` you can also use `A records` and `AAAA records` instead.
- First you need to specify which server should be serving your website. You can do this by setting an `A record` for IPv4 and an `AAAA record` for IPv6 which contains the ip address of the Codeberg Pages server. The servers' ip addresses are:
- `A record` which contains the IPv4 value `217.197.91.145`
- `AAAA record` which contains the IPv6 value `2001:67c:1401:20f0::1`
- `A record` which contains the IPv4 value `217.197.84.141`
- `AAAA record` which contains the IPv6 value `2a0a:4580:103f:c0de::2`
- Second, you need to setup a `TXT record` which contains the information from the `CNAME entry` which is your repository location as mentioned above. For example `[[branch.]repo.]user.codeberg.page`.
In the end, it should look like this:
@ -145,10 +145,10 @@ In the end, it should look like this:
</thead>
<tbody>
<tr>
<td>yourdomain.com</td><td>A</td><td>217.197.91.145</td>
<td>yourdomain.com</td><td>A</td><td>217.197.84.141</td>
</tr>
<tr>
<td>yourdomain.com</td><td>AAAA</td><td>2001:67c:1401:20f0::1</td>
<td>yourdomain.com</td><td>AAAA</td><td>2a0a:4580:103f:c0de::2</td>
</tr>
<tr>
<td>yourdomain.com</td><td>TXT</td><td>reponame.username.codeberg.page</td>
@ -194,8 +194,8 @@ For the DNS configuration:
- name `myself.example.com`, type `TXT`, data `frida.codeberg.page`
- otherwise, A/AAAA records must be used, together with one TXT record:
- name `myself.example.com`, type `A`, data `217.197.91.145`
- name `myself.example.com`, type `AAAA`, data `2001:67c:1401:20f0::1`
- name `myself.example.com`, type `A`, data `217.197.84.141`
- name `myself.example.com`, type `AAAA`, data `2a0a:4580:103f:c0de::2`
- name `myself.example.com`, type `TXT`, data `frida.codeberg.page`
### Personal/Organization site, apex domain
@ -219,8 +219,8 @@ For the DNS configuration, the CNAME SHOULD NOT be used, so:
- name `example.com`, type `TXT`, data `frida.codeberg.page`
- otherwise, A/AAAA records must be used, together with one TXT record:
- name `example.com`, type `A`, data `217.197.91.145`
- name `example.com`, type `AAAA`, data `2001:67c:1401:20f0::1`
- name `example.com`, type `A`, data `217.197.84.141`
- name `example.com`, type `AAAA`, data `2a0a:4580:103f:c0de::2`
- name `example.com`, type `TXT`, data `frida.codeberg.page`
### Project site, third-level domain
@ -247,8 +247,8 @@ For the DNS configuration:
- name `colormix-app.example.com`, type `TXT`, data `colormix.frida.codeberg.page`
- otherwise, A/AAAA records must be used, together with one TXT record:
- name `colormix-app.example.com`, type `A`, data `217.197.91.145`
- name `colormix-app.example.com`, type `AAAA`, data `2001:67c:1401:20f0::1`
- name `colormix-app.example.com`, type `A`, data `217.197.84.141`
- name `colormix-app.example.com`, type `AAAA`, data `2a0a:4580:103f:c0de::2`
- name `colormix-app.example.com`, type `TXT`, data `colormix.frida.codeberg.page`
### Project site, apex domain
@ -277,6 +277,6 @@ For the DNS configuration, CNAME SHOULD NOT be used:
- name `example.com`, type `TXT`, data `colormix.frida.codeberg.page`
- otherwise, A/AAAA records must be used, together with one TXT record:
- name `example.com`, type `A`, data `217.197.91.145`
- name `example.com`, type `AAAA`, data `2001:67c:1401:20f0::1`
- name `example.com`, type `A`, data `217.197.84.141`
- name `example.com`, type `AAAA`, data `2a0a:4580:103f:c0de::2`
- name `example.com`, type `TXT`, data `colormix.frida.codeberg.page`