You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: domain.qmd
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ These instructions assume that you already have ownership of the custom domain t
36
36
<ul>
37
37
<li> If this says something along the lines of "Your domain is not properly configured to support HTTPS" we will need to add additional records with your DNS provider </li>
38
38
<li> We strongly recommend following instructions from your DNS provider. You should look up "HTTPS record for \[your DNS provider\]" in Google and follow any of their documentation. </li>
39
-
<li> For example, on GoDaddy, you can add an HTTPS record where the name is @ and the value is **TO DO** </li>
39
+
<li> For example, on GoDaddy, you can add an HTTPS record where the name is @ and the value is your site's domain (e.g., mysite.com) </li>
40
40
</ul>
41
41
<li> If you run into any additional problems, you may want to ensure that there are no additional A records aside from the ones listed above. This may be a problem if you have previously had your site hosted through a service separate from GitHub pages. </li>
42
42
<li> Some common warning messages that you may see when GitHub pages is connecting to your site include "DNS valid for primary" or "DNS check in progress" -- these are both OK, and should go away once your site is connected. </li>
0 commit comments