VMware VirtualCenter Server Service Hung at Starting (No such host is known)

After a gracefully rebooting our vCenter server, the VMware Virtual Center Service was hung in the "Starting" status.  A quick look at Event Viewer showed the very common Event ID 1000:

On a Windows Server 2012 R2 box, the vCenter logs are located in the following location:

C:\ProgramData\VMware\VMware Virtual Center\Logs\vpxd.log

The log showed the following warnings:

2017-03-24T19:42:30.743-05:00 [04304 warning 'Default'] Failed to resolve address; <resolver p:0x000000000xxxxx, 'mypscserver.mydomain.com:7444'>, e: system:11001(No such host is known)

2017-03-24T19:42:30.743-05:00 [04304 error 'HttpConnectionPool-000001'] [ConnectComplete] Connect failed to <cs p:000000000af76900, TCP:mypscserver.mydomain.com::7444>; cnx: (null), error: class Vmacore::SystemException(No such host is known)

We are currently upgrading our vSphere infrastructure to version 6.5.  One of the first steps performed was to upgrade our external 5.5 SSO server to a 6.5 PSC appliance.  It appears the PSC appliance did not register properly in DNS.  No ping replies...

After adding a static entry in DNS and allowing time for the entry to propagate, I was able to successfully start the vCenter service.

I then performed a graceful restart of the vCenter server to make absolutely sure the vCenter server starts successfully.