Configure GitHub Enterprise with the DNS nameservers and hostname required in your network. You can also configure a proxy server or firewall rules. You must allow access to certain ports for administrative and user purposes.
By default, GitHub Enterprise 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.
GitHub Enterprise 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.
We recommend setting a hostname for your appliance instead of using a hard-coded IP address.
Ensure that your domain settings are properly configured before booting up your GitHub Enterprise instance for the first time.
You can configure Transport Layer Security (TLS) on your GitHub Enterprise instance so that you can use a certificate that is signed by a trusted certificate authority.
You can set up subdomain isolation to securely separate user-supplied content from other portions of your GitHub Enterprise appliance.
A proxy server provides an additional level of security for your GitHub Enterprise instance.
You can view default firewall rules and customize rules for your GitHub Enterprise instance.
Open network ports selectively based on the network services you need to expose for administrators, end users, and email support.
Use a load balancer in front of a single GitHub Enterprise appliance or a pair of appliances in a High Availability configuration.