Commit 55b8c498 authored by Nick Gaskill's avatar Nick Gaskill

Merge branch 'fix-pages-custom-domain-docs' into 'master'

Clarify that Pages domain should be pointing at Pages's IP

See merge request gitlab-org/gitlab!50613
parents 71a8a6a8 5380f934
...@@ -101,6 +101,27 @@ Where `example.io` is the domain GitLab Pages is served from, ...@@ -101,6 +101,27 @@ Where `example.io` is the domain GitLab Pages is served from,
`192.0.2.1` is the IPv4 address of your GitLab instance, and `2001:db8::1` is the `192.0.2.1` is the IPv4 address of your GitLab instance, and `2001:db8::1` is the
IPv6 address. If you don't have IPv6, you can omit the AAAA record. IPv6 address. If you don't have IPv6, you can omit the AAAA record.
#### Custom domains
If support for custom domains is needed, the Pages root domain and its subdomains should point to
the secondary IP (which is dedicated for the Pages daemon). `<namespace>.<pages root domain>` should
point at Pages directly. Without this, users aren't able to use `CNAME` records to point their
custom domains to their GitLab Pages.
For example, an entry could look like this:
```plaintext
example.com 1800 IN A 192.0.2.1
*.example.io. 1800 IN A 192.0.2.2
```
This example contains the following:
- `example.com`: The GitLab domain.
- `example.io`: The domain GitLab Pages is served from.
- `192.0.2.1`: The primary IP of your GitLab instance.
- `192.0.2.2`: The secondary IP, which is dedicated to GitLab Pages.
NOTE: NOTE:
You should not use the GitLab domain to serve user pages. For more information see the [security section](#security). You should not use the GitLab domain to serve user pages. For more information see the [security section](#security).
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment