OS Install Error: 'Could not resolve host: api.synergy'

OS Install Error: “Could not resolve host: api.synergy” #

SynergyCP deploys a DHCP server at each location to have a DNS server as well. The DNS server maps the domain “api.synergy” to your custom SynergyCP API domain. This error occurs when the DHCP server is not responding correctly with the API domain.

Please be advised that every statement of “DHCP server” refers to the DHCP server provided by SynergyCP for the purposes of automated OS reloads. It does not refer to any other DHCP server present on your network.

The most likely reasons for this are:

  • The deployment DHCP server isn’t configured with the API domain correctly; this is supposed to happen automatically. You could try changing the OS Reloads > Deploy DHCP servers > DHCP server > Hostname to anything else, saving, and then changing it back and saving again. This triggers the sync process.
  • You could also try updating the DHCP server to the latest version by running the update script on the DHCP server (which is usually your master SynergyCP server): wget https://install.synergycp.com/bm/pxe-dhcp-server.sh -O - | bash. If you’ve changed the IP address of your DHCP server, this update script will update it with the correct DNS server IP.
  • There is another DHCP server on your network that this server is picking up. You could try running ipconfig /a in that shell you see to see if it’s picking up the right IP from SynergyCP and the right DNS server (which should be the DHCP server’s IP), or use dhcpdump on your SynergyCP DHCP server to confirm that it is the only DHCP server responding.
  • The OS was not able to establish a DHCP connection because it does not support the network card of the server. On Windows, this could appear as an IP allocation of 169.254.. - this is the Windows version of no DHCP connection available. In this case, try making sure that the ethernet connection used for PXE booting is on a network card that Windows supports without extra drivers (required for PXE booting). If you need another network card, e.g. a 10gbps one, you’ll need two IP allocations on the server and the 10gbps will need to be a secondary network card.