Are you able to ping vcsa.dc.local? Is your laptop in a different Domain than dc.local? Have you tried to connect from another PowerCLI client, perhaps on the same vLAN if that's an option?
Yes I can ping vcsa.dc.local (via IP only and NOT the FQDN for which I had posted question here Can't access the vCSA via Web UI from host, cant get Stage 2 started and somewhat similar question here new sytand-alone vCenter Server DNS requirement ? which I got sorted by using IP instead of FQDN and it has been IP ever since.)
The laptop is the host for vCSA (vCSA is running in Workstation).
I will try to access it from a different VM and update here, thanks for the hint.
As a quick test, add an entry in your Hosts file for that DNS to IP resolution.
Thanks for the tip, I was trying to make it work for a long time, tried it via hosts file as well did not work.
Just now added in hosts file 192.168.169.8 vcsa.dc.local and now it works from the host PC.
Just for understanding, am I correct in understanding that because my DNS is 18.104.22.168 (set by my DHCP, beyond my control) my vcsa.dc.local is not being resolved by my windows resolver and the query is actually being redirected to 22.214.171.124,. I know this from my nslookup query which resulted in a reply from 126.96.36.199 and not locally ?!
Yes that is correct. According to MS rules, DNS uses Hosts files first before Primary\Secondary DNS servers.