Article version: Enterprise Server 2.15

This version of GitHub Enterprise will be discontinued on This version of GitHub Enterprise was discontinued on 2019-10-16. 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.

Note: If you change the hostname of your GitHub Enterprise Server instance, images and other assets that use absolute URLs, such as embedded issues, will not load. For a basic server rename, we recommend keeping the old hostname as a CNAME on the SSL certificate to ensure assets continue to load from the old hostname.

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.

    $ ssh -p 122 admin@HOSTNAME
  2. To edit your nameservers, enter:

    $ sudo vim /etc/resolvconf/resolv.conf.d/head
  3. Append any nameserver entries, then save the file.

  4. After verifying your changes, save the file.

  5. To add your new nameserver entries to your GitHub Enterprise Server instance, enter:

    $ sudo service resolvconf restart

Ask a human

Can't find what you're looking for?

Contact us