Fixing DNS resolution in my podman network

[flixman]

I have a network that gets created like /usr/bin/podman network create --ignore systemd-harbor. When created, this is how it looks like:

[
     {
          "name": "systemd-harbor",
          "id": "4665c0346e4830aae5658367a5af3cebfbe0d841fde664d49e799e33437221d9",
          "driver": "bridge",
          "network_interface": "podman2",
          "created": "2025-08-26T07:54:31.828235373+02:00",
          "subnets": [
               {
                    "subnet": "10.90.0.0/24",
                    "gateway": "10.90.0.1"
               }
          ],
          "ipv6_enabled": false,
          "internal": false,
          "dns_enabled": true,
          "ipam_options": {
               "driver": "host-local"
          },
          "containers": {}
     }
]

Then I get some containers attached to it, like portal and redis, and one is not able to find the other. The resolv.conf file seems to be picking my current gateway (192.168.123.1), an internal veth (10.255.255.1) and another nameserver that (I guess) comes from podman itself?

$ podman exec -it core cat /etc/resolv.conf 
nameserver 169.254.1.1
nameserver 10.255.255.1
nameserver 192.168.123.1

if I set the dns to be only 169.254.1.1 for those containers, the /etc/resolv.conf comes back clean... but still they cannot resolve one another. The network backend I'm using is slirp4netns (netavark is stated as backend, but I think that does not apply because the containers are running rootless?).

Why are all those interfaces popping up? Why containers cannot resolve one another? Does anybody have any suggestion?

[flixman]

I am an idiot: the containers were not connected to the network (palm)