Configuring network settings
Configure GitHub Enterprise Server 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 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.
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.
You can provide reliable access to your GitHub Enterprise Server instance by assigning a hostname that's accessible over your network.
If you want to change the hostname for an existing GitHub Enterprise Server instance, you must restore the settings and data to a new instance.
Ensure that your domain settings are properly configured before booting up your GitHub Enterprise Server instance for the first time.
A proxy server provides an additional level of security for your GitHub Enterprise Server instance.
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.
Use a load balancer in front of a single GitHub Enterprise Server instance or a pair of instances in a High Availability configuration.
GitHub Enterprise Server automatically synchronizes its clock by connecting to NTP servers. You can set the NTP servers that are used to synchronize the clock, or you can use the default NTP servers.