We are small users with only 3 hosts. 2 hosts are running ESXi 4.1, and I am in the process of installing a new third host. We currently rely on Data Recovery and so the new, allegedly more robust, Data Protection appliance was of particular interest. I am therefore trying to upgrade from vSphere 4.1 to 5.1. In order to do so I have to stop using Data Recovery and start using Data Protection instead ( They cannot bee run in parallel as vCenter 5.1 does not support Data Recovery which requires a vCenter connection to work, and vCenter 4.1 does not support ESXi 5.1 ).
I have installed a Data Protection appliance on the new ESXi 5.1 host, but it returns the error " IP/DNS could not be reolved" at the configuration stage.
We are using a typical Windows Server 2003/2008 active directory single domain and the relevant DNS entries have been added manually for all the VMWare Linux appliances. vCenter 5.1 is on a Windows 2008 R2 server. The first problem is that it is not clear whether vDP is case sensitive ( Windows AD is of course not case sensitive, so it would seem crazy for it to be so. However, I have seen suggestions that it is. For now I am assuming that it is not.)
The usual ping and nslookup checks reveal the following:
Pings work between vDP and vCenter for IP, hostname and FQDN.
Ping and nslookup work from Windows servers and PC's for all 3 flavours, whether to a windows machine or Linux appliance.
However, ping and nslookup from a VMWare Linux appliance works for IP and FQDN, but DOES NOT work for a hostname. This is the same from vDP 5.1, vDR 2 or vMA 4.1. Nevertheless vMA and vDR both work fine. It is only vDP which seems to have problems as a result.
I have submitted a VMWare support request a week ago but so far no joy. If I cannot resolve this soon I will have to give up and go back to vSphere 4.1 for our new host.
Is there anybody else with a Windows 2008 AD who has installed Data Protection please?
Is there any way of adding the domain suffix to the hostname automatically in a Linux appliance?