Netavark was recently changed, when being used with podman, to remove the dns.podman search domain in detriment of using the host's search domain in the container. This leads to a possible DNS resolve confusion in some scenarios where the container created using podman have the same hostname as an external service. This may lead to containers communicating to unexpected servers instead of the desired one.
Upstream commit fixing this issue: https://github.com/containers/netavark/pull/1256/commits/03f12695a696c7fe407eefebd7d5ad3cf2e934fe