No resolution.  I just changed all the clients to start using the FQDN instead.  Sounds like a bug or "new feature" added in v2.2 then.  Thanks for verifying that it worked in 5.3.  I will probably open a ticket with VMware when I get a chance.  Just not a high priority right now.

Chris