IPv6 Container outbound precedence

[imp1sh]

Podman Version: 4.3.1+ds1-8+deb12u1
aardvark and netavark: 1.4.0-3

podman network:

podman network inspect podmannet
[
     {
          "name": "podmannet",
          "id": "cbea01b7398ff5fdf95faf1a5275d62d0691f0821a7906f4dd36bfe054956b53",
          "driver": "bridge",
          "network_interface": "podman1",
          "created": "2023-11-01T23:35:21.231236772+01:00",
          "subnets": [
               {
                    "subnet": "10.89.0.0/24",
                    "gateway": "10.89.0.1"
               },
               {
                    "subnet": "fda9:92d6:18ac:e10e::/64",
                    "gateway": "fda9:92d6:18ac:e10e::1"
               }
          ],
          "ipv6_enabled": true,
          "internal": false,
          "dns_enabled": true,
          "ipam_options": {
               "driver": "host-local"
          }
     }
]

So basically all my services running in podman are reachable dual-stack.
Yet a big problem arises when a network connection is being initiated from within any container. It will ALWAYS use IPv4 instead of IPv6 first, even when a host record has both A and AAAA records.
What can I do to resolve that? It has really big implications, because for v4 I would need to have DNAT rules that would even conflict with each other, as there is v4 address shortage.

# host www.heise.de
www.heise.de has address 193.99.144.85
www.heise.de has IPv6 address 2a02:2e0:3fe:1001:7777:772e:2:85
# ping6 www.heise.de
PING www.heise.de(www.heise.de (2a02:2e0:3fe:1001:7777:772e:2:85)) 56 data bytes
64 bytes from www.heise.de (2a02:2e0:3fe:1001:7777:772e:2:85): icmp_seq=1 ttl=56 time=9.92 ms
^C
--- www.heise.de ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 9.921/9.921/9.921/0.000 ms
# ping www.heise.de
PING www.heise.de (193.99.144.85) 56(84) bytes of data.
64 bytes from www.heise.de (193.99.144.85): icmp_seq=1 ttl=247 time=10.3 ms

Thank you for your ideas!

[imp1sh]

Is it maybe possible that for outbound connections IPv4 is preferred because the IPv6 address is ULA (RFC 6724)?

[imp1sh]

It turns out that is the very reason. So I hope this helps if someone else runs into this nasty problem.