we are in the process of preparing for the upgrade of our existing environment from vSphere 5.0 to vSphere 5.1. I’ve attempted a mock installation of SSO Server and have also run the SSO pre-installation check script and we have discovered an issue in our environment. In order to explain the issue I’ll need to provide a bit of background information on DNS configuration in our environment.
There are two DNS solutions in our environment, Corporate DNS (UNIX) and DDNS (Dynamic DNS – Active Directory). DDNS was deployed with introduction of AD, prior to than all systems were using Corporate DNS. When DDNS was introduced DNS services were not migrated to it, instead DDNS is used solely by AD and Windows Server/Client environment. Additionally DDNS is not configured for reverse lookup DNS resolution, all such requests are forwarded to Corporate DNS.
As you may or may not be aware one of the requirements for SSO deployment is to have reverse lookup DNS configured and for each DC and SSO server to have a properly configured PTR records (http://kb.vmware.com/kb/2033880) . Since we are not using DDNS for reverse lookup resolution PTR records are non-existent. Consequently the installation of SSO throws warning regarding the reverse lookup DNS failure and the SSO pre-installation check script displays warnings re “IP Address to Name Check” for the SSO Server and every DC in the domain.
we are just wondering if anybody else had come across this issue? and if so what they did to resolved the issue
any help would be appreciated