![]() ![]() When using an apex domain, we recommend configuring your GitHub Pages site to host content at both the apex domain and that domain's www subdomain variant. > EXAMPLE.COM 3600 IN AAAA 2606:50c0:8003::153Ĭonfiguring an apex domain and the www subdomain variant Confirm that the results match the IP addresses for GitHub Pages above. To confirm that your DNS record configured correctly, use the dig command, replacing EXAMPLE.COM with your apex domain. To create AAAA records, point your apex domain to the IP addresses for GitHub Pages.To create A records, point your apex domain to the IP addresses for GitHub Pages.For more information about the default domain for your site, see " About GitHub Pages." To create an ALIAS or ANAME record, point your apex domain to the default domain for your site.For more information about how to create the correct record, see your DNS provider's documentation. You can also create AAAA records for IPv6 support. ![]() Navigate to your DNS provider and create either an ALIAS, ANAME, or A record. ![]() For more information about your publishing source, see " Configuring a publishing source for your GitHub Pages site." If you are publishing your site with a custom GitHub Actions workflow, no CNAME file is created. If you are publishing your site from a branch, this will create a commit that adds a CNAME file to the root of your source branch. Under "Custom domain", type your custom domain, then click Save. In the "Code and automation" section of the sidebar, click Pages. If you cannot see the "Settings" tab, select the dropdown menu, then click Settings. Under your repository name, click Settings. On GitHub, navigate to your site's repository. ![]() If you are using an apex domain as your custom domain, we recommend also setting up a For example, if you configure as the custom domain for your site, and you have GitHub Pages DNS records set up for the apex and Note that automatic redirects only apply to the For more information, see " Configuring a subdomain." To set up an apex domain, such as, you must configure a custom domain in your repository settings and at least one ALIAS, ANAME, or A record with your DNS provider. For more information, see " Securing your GitHub Pages site with HTTPS." It can take up to 24 hours before this option is available. Optionally, to enforce HTTPS encryption for your site, select Enforce HTTPS. For more information, see " Troubleshooting custom domains and GitHub Pages." If you use a static site generator to build your site locally and push the generated files to GitHub, pull the commit that added the CNAME file to your local repository. To confirm that your DNS record configured correctly, use the dig command, replacing with your subdomain. For more information, see " Verifying your custom domain for GitHub Pages." For example, if you verify this prevents someone from using a. but they could still take over b.a. (which is covered by the wildcard DNS record). These records put you at an immediate risk of domain takeovers, even if you verify the domain. Warning: We strongly recommend that you do not use wildcard DNS records, such as *. ![]()
0 Comments
Leave a Reply. |