I have a MAAS setup that works perfectly fine as a VM on Vmware Workstation. When I do a nslookup on a node known by MAAS, the resolution is successfull (with maas node IP in resolv.conf, followed by "search maas").
But when I migrate this exact same Maas setup into Vmware ESXi, I have systematically a "NXDOMAIN" error. A nmap performed from another vm running on ESXi give me this :
Nmap scan report for maas.maas (192.168.2.2)
Host is up (0.000092s latency).
Not shown: 993 closed ports
PORT STATE SERVICE
22/tcp open ssh
53/tcp open domain
80/tcp open http
3128/tcp open squid-http
3260/tcp open iscsi
7911/tcp open unknown
8000/tcp open http-alt
Nmap done: 1 IP address (1 host up) scanned in 0.03 seconds
So, my dns service is running. I can't figure out what is going on !
I'm not sure to understand your question ; to bring some details on my setup, MAAS (MAAS | Metal as a Service), which is itself a DNS provider, runs on a VM inside ESXi. The internal DNS of MAAS is used by machines it has deployed (those deployments can be virtual machines running on ESXi, or physical machines).
So when MAAS runs in VmWare Workstation, its internal DNS works perfectly with machines it deployed. But MAAS internal DNS do not worked anymore when running inside ESXi (cf nslookup not working anymore when trying to resolve hostname of machine B from machine A, with MAAS configure as a DNS in resolv.conf of machine A and B).
I guess it could be the ESXi DNS configuration causing some troubles ?