问题
This morning I got emails for each of my Gitlab Pages that are hosted on custom domains, saying that the domain verification failed.
That's fine, because I don't think I ever verified them in the first place - good on Gitlab for getting this going.
When I head on over the the Settings>Pages>Domain_Details on each repo, I see the instructions to create the following record:
_gitlab-pages-verification-code.blog.ollyfg.com TXT gitlab-pages-verification-code={32_digit_long_code}
On creating this record, and clicking the "Verify Ownership" button, I get the message "Failed to verify domain ownership".
I have ensured that the record is set, and calling
dig -t txt +short _gitlab-pages-verification-code.blog.ollyfg.com
Returns:
"gitlab-pages-verification-code={same_32_digit_long_code}"
Is this a bug in Gitlab? Am I doing something wrong?
Thanks!
回答1:
Wait for sometime, it worked for me. Initially, having the same problem as you mentioned.
Also, you may find this page useful: https://gitlab.com/help/user/project/pages/getting_started_part_three.md#dns-txt-record
It might be worthwhile, trying with:
blog.ollyfg.com
instead of: _gitlab-pages-verification-code.blog.ollyfg.com
回答2:
Here is how to get a subdomain.domain.com point to namespace.gitlab.io/project-name with Gandi.
The CNAME and TXT records generated by GitLab when adding a new subdomain to a project via Settings > Pages > New Domain did not work in my case. The exact non-working records were mysubdomain.mydomain.com CNAME mynamespace.gitlab.io. and _gitlab-pages-verification-code.mysubdomain.mydomain.com TXT gitlab-pages-verification-code=00112233445566778899aabbccddeeff.
Modifications like mysubdomain CNAME mynamespace.gitlab.io. (with and without a dot at the end) did not work, either (ping mysubdomain.mydomain.com said unknown host).
Using an A record and a TXT record with only the subdomain in the record's name field does work in my case. Here are the exact working records:
mysubdomain 1800 IN A 35.185.44.232
mysubdomain 1800 IN TXT "gitlab-pages-verification-code=00112233445566778899aabbccddeeff"
Note that the namespace.gitlab.io IP address has changed from 52.167.214.135 to 35.185.44.232 in 2018.
Wait as least 30 minutes to get the records propagate.
In my case GitLab also verified the domain automatically, I did not need to click the Verify button.
回答3:
The docs (and the verification page) were a little confusing for me. Here's what worked for me, on GoDaddy:
A Record:
Name: @
Value: 35.185.44.232
CNAME:
Name: example.com
Value: username.gitlab.io
TXT Record:
Name: @
Value: gitlab-pages-verification-code=00112233445566778899aabbccddeeff
Verified with Gitlab, and also:
dig -t txt +short example.com
回答4:
I really get a hard time to make it work. But in the end below settings worked for me.
GoDaddy
domain.com
A record
+-----------+---------------------+
| Host | @ |
+-----------+---------------------+
| Points To | 35.185.44.232 |
+-----------+---------------------+
To Verify your domain Add TXT record
TXT record
+-----------+-----------------------------------------------------------------+
| Host | @ |
+-----------+-----------------------------------------------------------------+
| TXT Value | gitlab-pages-verification-code=00112233445566778899aabbccddeeff |
+-----------+-----------------------------------------------------------------+
subdomain.domain.com
CNAME record
+-----------+---------------------+
| Host | subdomain |
+-----------+---------------------+
| Points To | namespace.gitlab.io |
+-----------+---------------------+
To Verify your domain Add TXT record
TXT record
+-----------+-----------------------------------------------------------------+
| Host | _gitlab-pages-verification-code.subdomain |
+-----------+-----------------------------------------------------------------+
| TXT Value | gitlab-pages-verification-code=00112233445566778899aabbccddeeff |
+-----------+-----------------------------------------------------------------+
Note subdomain and verification code will be found under settings>page (create/details) GitLab Pages IP on GitLab.com has been changed from 52.167.214.135 to 35.185.44.232 in 2018
回答5:
For GoDaddy (April 2020), I had to do the following:
|Type |Name |Value |
-----------------------------------------------------------------------------------
|A |example.com (or @) |35.185.44.232 |
|TXT |_gitlab-pages-verification-code|gitlab-pages-verification-code=blahblahblah|
|A |www |35.185.44.232 |
|CNAME|www.example.com |example.gitlab.io |
|TXT |_gitlab-pages-verification-code|gitlab-pages-verification-code=blahblahblah|
| |(or _gitlab-pages.verification-| |
| |code.www) | |
While the documentation said to use _gitlab-pages-verification-code.example.com and _gitlab-pages-verification-code.www.example.com, those did not work for me, and I could see within seconds after changing and re-checking my verification status that it changed from unverified to verified, and vice versa.
来源：https://stackoverflow.com/questions/48913026/gitlab-pages-failed-to-verify-domain-ownership