I create a new VM with 1024 MB and now i have zero problem. Thanks for your help :)

instructions https://docs.netgate.com/pfsense/en/latest/virtualization/virtualizing-pfsense-with-vmware-vsphere-esxi.html

LAN usually has a Default Allow All rule, so LAN clients should be able to get anywhere. Provide screenshots of your LAN & DMZ network details as well as your LAN firewall rules.

So your saying pfsense without any dns is reaching out to a specific IP? So the IP must be hard coded into pfsense to check for X? I don't think so to be honest, hard coding IPs is horrible coding! Lets see these logs, or the IP that its reaching out to.. And we can prob figure out what is going on.. But I would be very surprised if the pfsense dev's hardcoded an IP into anything they are running. Best would also be these sniffs you took. You have no packages installed? You sure its just not the ping to the gateway of pfsense wan? That would be reaching out to an IP without dns to resolve it.. You do know that pfsense even if you turn off unbound, will try and grab dns from dhcp on its wan. And then would attempt to use that for dns.. Also how are you sure its not something on the lan side trying to get to X? What about NTP? If pfsense at any time had dns, it would of resolved some IPs in the ntp.pool and be trying to set time with those, etc. TL;DR going to need way more info to try and help you figure out what your seeing. Also, I have a few pfsense vms I could fire up and try and duplicate what your doing/seeing..

i am also having issue with carp running kvm/qemu with libvirt. the devices see each other and choose master and slave respectively but if i turn one off the clients cannot access the virtual ip anymore. is this fix applicable in my case and if so how do i do it?

I may have figured out the problem with bridging... MAC address spoofing must be enabled on all the Hyper-V vswitches that are being bridged

I came across similar NIC ordering issue some time ago. When I added more than 4 vmxnet3 adapters to the machine, FreeBSD numbered interfaces differently in comparison to VM ethernet adapter order, that issue is described here. When I used E1000 interfaces, the problem disappeared. I had to use workaround script that renamed vmx interfaces in FreeBSD based on their mac address, so that interface order was the same on VM and FreeBSD. This is however something different. I'm not touching interfaces on the VM, I'm just unassigning/disabling interfaces in pfSense GUI under Interfaces -> Assignments. Though it definitely bears some similarity with aforementioned NIC order bug (meaning that everything is fine with only 4 interfaces on the machine).

pfSense just needs to see link down by whatever method your hypervisor allows.

You could edit the post title which is in your first post and prepend it with [SOLVED] or [RESOLVED], depending on your preference.

Thanks for your help!