/HCX Manager and HCX Connector DNS are not working after deploying

HCX Manager and HCX Connector DNS are not working after deploying

When I deploy the latest versions of HCX Manager 4.4.0-build 20427536 and HCX Connector 4.4.2-build-20502808, for some reason, DNS is not set on the deploy of the OVA, and HCX Manager and HCX Connector DNS are not working after deploying.

When I try to connect the HCX to vCenter (as the first option), I always get this error: VCenter vCenter-Name is not reachable. Error communicating to VC endpoint vCenter-Name:443. Reason: UnknownHostException

HCX Manager and HCX Connector DNS are not working after deploying

The first time I tough I added the wrong DNS or forgot to add it (not possible since it is mandatory), but then I was sure this was something on the deployment since I am pretty sure I did on the latest deployments.

I canceled the connection to the vCenter and checked the DNS settings, and as you can notice in the next image, it is empty, but the domain is ok.

HCX Manager and HCX Connector DNS are not working after deploying

So we need to add the DNS here.

HCX Manager and HCX Connector DNS are not working after deploying

After you add the DNS, HCX tells you that you need to reboot the HCX Appliance so that this change is effective, but that is not mandatory. You can login to HCX Appliance SSH and restart the resolve services with the following command:

  • systemctl restart systemd-networkd
  • systemctl restart systemd-resolved

HCX Manager and HCX Connector DNS are not working after deploying

Note: If you try to use the command nslookup to test your DNS in the command line, it will not work. Since it is not installed in this Photon OS, but if you still want to use it, you can install it by running the command: tdnf install bindutils 

After restarting the services, I returned to HCX and tried the connection again to vCenter using the FQDN all was ok, and I could connect to vCenter, SSO, NSX, etc.

Again this happens not only in HCX Manager deployment but also in a couple of HCX Connecters. I don’t know if anyone else had this issue and if it is a bug.

UPDATE 29/09

I try again in more HCX implementations, and this time when deploying the OVA Appliance, I only add one DNS entry, not two separated by a comma, which is the trick. DNS in the HCX was set, and I added the second one when the Appliance was deployed.

So it seems to be a bug when you add more than one DNS entry in the OVA file it doesn’t set the DNS. I saw this some years ago with one vCD OVA version. Should this be the same?

Share this article if you think it is worth sharing. If you have any questions or comments, comment here, or contact me on Twitter.

©2022 ProVirtualzone. All Rights Reserved
By | 2022-09-30T12:29:55+02:00 September 28th, 2022|HCX, NSX, VCF, VMware Posts|0 Comments

About the Author:

I have over 20 years of experience in the IT industry. I have been working with Virtualization for more than 15 years (mainly VMware). I recently obtained certifications, including VCP DCV 2022, VCAP DCV Design 2023, and VCP Cloud 2023. Additionally, I have VCP6.5-DCV, VMware vSAN Specialist, vExpert vSAN, vExpert NSX, vExpert Cloud Provider for the last two years, and vExpert for the last 7 years and a old MCP. My specialties are Virtualization, Storage, and Virtual Backup. I am a Solutions Architect in the area VMware, Cloud and Backup / Storage. I am employed by ITQ, a VMware partner as a Senior Consultant. I am also a blogger and owner of the blog ProVirtualzone.com and recently book author.

Leave A Comment