Container host has DNS, but container does not?

Not sure how to troubleshoot this. But my container host has this in the DNS:

# resolvectl status
         Protocols: LLMNR=resolve -mDNS +DNSOverTLS DNSSEC=yes/supported
  resolv.conf mode: foreign
Current DNS Server:
       DNS Servers:

Link 2 (eth0)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS +DNSOverTLS DNSSEC=yes/supported

I start my container with:

podman run --dns --rm -it fedora cat /etc/resolv.conf

And as you can see it uses for DNS, but dnf cannot resolve any URLs.

This container host is freshly installed. firewall-cmd has log-denied messages on, I see nothing blocked by the firewall. Forwarding is on in firewalld. I also enabled net.ipv4.ip_forward = 1 as a test with net.ipv6.conf.all.forwarding = 1, but no difference.

Anything else I should check?

Super odd. But when using --dns the container does have DNS. Since I’m happy it works and don’t have time to find out why, I’ll leave it like this for now. It’s strange, since the container host can use, so there is no upstream filtering going on.