Configuring the IP address using the virtual machine console→
By default, GitHub Enterprise Server retrieves network settings via the dynamic host configuration protocol (DHCP). If your platform supports it, or if DHCP is unavailable, you can also configure the network settings using the virtual machine console.
Configuring DNS nameservers→
GitHub Enterprise Server uses the dynamic host configuration protocol (DHCP) for DNS settings when DHCP leases provide nameservers. If nameservers are not provided by a dynamic host configuration protocol (DHCP) lease, or if you need to use specific DNS settings, you can specify the nameservers manually.
Configuring a hostname→
We recommend setting a hostname for your appliance instead of using a hard-coded IP address.
Validating your domain settings→
Ensure that your domain settings are properly configured before booting up your GitHub Enterprise Server instance for the first time.
You can configure Transport Layer Security (TLS) on your GitHub Enterprise Server instance so that you can use a certificate that is signed by a trusted certificate authority.
Enabling subdomain isolation→
You can set up subdomain isolation to securely separate user-supplied content from other portions of your GitHub Enterprise Server appliance.
Configuring an outbound web proxy server→
A proxy server provides an additional level of security for your GitHub Enterprise Server instance.
Configuring built-in firewall rules→
You can view default firewall rules and customize rules for your GitHub Enterprise Server instance.
Open network ports selectively based on the network services you need to expose for administrators, end users, and email support.
Using GitHub Enterprise Server with a load balancer→
Use a load balancer in front of a single GitHub Enterprise Server appliance or a pair of appliances in a High Availability configuration.