I don't think this was related directly to the Enhance update. There are a few issues I've seen lately in support tickets.
Postfix resolv.conf
Postfix copies the /etc/resolv.conf to its chroot /var/spool/postfix/etc/resolv.conf on startup. A restart would happen after a Postfix package update. If the /etc/resolv.conf was empty at that point, the postfix resolv.conf might also be empty. Running systemctl restart postfix would fix it assuming /etc/resolv.conf is now correct.
Postfix postdrop binary in overlay dir
Some servers that were upgraded from Ubuntu 22.04 to 24.04 or Enhance v11 to v12 might have an old copy of the postfix postdrop binary in the container overlay directory. As root, run ls /var/local/enhance/containers/*/*/overlay/usr/sbin/postdrop - there should be no results. If any are found, remove those files and restart the affected containers through the Enhance UI.
If problems persist please send a support ticket.