Skip to main content

This version of GitHub Enterprise was discontinued on 2022-10-12. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

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.

The nameservers you specify must resolve your GitHub Enterprise Server instance's hostname.

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.

Configuring nameservers using the virtual machine console

  1. Using your virtualization platform tools, open the virtual machine console. GitHub Enterprise console
  2. To start your network setup, press S.
  3. Configure nameservers for your instance.
  4. To finish configuring your settings, press D.

Configuring nameservers using the administrative shell

  1. SSH into your GitHub Enterprise Server instance. If your instance comprises multiple nodes, for example if high availability or geo-replication are configured, SSH into the primary node. If you use a cluster, you can SSH into any node. For more information about SSH access, see "Accessing the administrative shell (SSH)."

    $ ssh -p 122 admin@HOSTNAME
  2. To edit your nameservers, use the ghe-setup-network command in visual mode. For more information, see "Command-line utilities."

    ghe-setup-network -v
  3. To add your new nameserver entries to your GitHub Enterprise Server instance, run the following:

    sudo service resolvconf restart
    sudo service dnsmasq restart