If you configure a hostname instead of a hard-coded IP address, you will be able to change the physical hardware that your GitHub Enterprise Server instance runs on without affecting users or client software.
The hostname setting in the Management Console should be set to an appropriate fully qualified domain name (FQDN) which is resolvable on the internet or within your internal network. For example, your hostname setting could be
github.companyname.com. Web and API requests will automatically redirect to the hostname configured in the Management Console. Note that
localhost is not a valid hostname setting.
Hostnames must be less than 63 characters in length per Section 2.3.4 of the Domain Names Specification RFC.
After you configure a hostname, you can enable subdomain isolation to further increase the security of your GitHub Enterprise Server instance. For more information, see "Enabling subdomain isolation."
For more information on the supported hostname types, see Section 2.1 of the HTTP RFC.
Warning: Do not change the hostname for GitHub Enterprise Server after initial setup. Changing the hostname will cause unexpected behavior, up to and including instance outages.
From an administrative account on GitHub Enterprise Server, in the upper-right corner of any page, click .
If you're not already on the "Site admin" page, in the upper-left corner, click Site admin.
In the " Site admin" sidebar, click Management Console.
In the "Settings" sidebar, click Hostname.
Under "Hostname", type the hostname you'd like to set for your GitHub Enterprise Server instance.
To test the DNS and SSL settings for the new hostname, click Test domain settings.
If you don't receive a green checkmark next to all entries, review your configuration for the setting that failed. For more information, see "Configuring DNS nameservers."
Under the "Settings" sidebar, click Save settings.
Note: Saving settings in the Management Console restarts system services, which could result in user-visible downtime.
Wait for the configuration run to complete.
To help mitigate various cross-site scripting vulnerabilities, we recommend that you enable subdomain isolation for your GitHub Enterprise Server instance after you configure a hostname. For more information, see "Enabling subdomain isolation."