Issues with apex custom domains
Relevant issue https://gitlab.com/gitlab-com/support-forum/issues/569
This should be better documented and fixed in the Details page when adding a new domain. If the new domain is not a subdomain, the following info should show an A record with the IP address. I learned this the hard way when my MX records were broken.
Our current IP that the pages daemon listens to is 104.208.235.32.
Few links:
- https://devcenter.heroku.com/articles/apex-domains
- https://serverfault.com/questions/613829/why-cant-a-cname-record-be-used-at-the-apex-aka-root-of-a-domain
- https://stackoverflow.com/questions/16022324/how-to-setup-dns-for-an-apex-domain-no-www-pointing-to-a-heroku-app
cc @ayufan
Activity
mentioned in issue gitlab-com/support-forum#569 (closed)
mentioned in merge request gitlab-com/www-gitlab-com!1580 (merged)
mentioned in issue #454 (closed)
@jnijhof @pcarranza Can we make sue that this address never changes? If so, we could show to create an A-record.
Then we could advise to:
- Create
Apointing to104.208.235.32. - Advise to use CNAME flattening on CloudFlare: https://blog.cloudflare.com/introducing-cname-flattening-rfc-compliant-cnames-at-a-domains-root/
- Create
@ayufan the ipnumber will not be changed but since we are on Azure we don't have the 100% garante that it won't in future.
mentioned in issue gitlab-com/operations#181 (closed)
changed milestone to %8.17
mentioned in issue gitlab-com/gitlab-docs#69 (closed)
