Rootful Networking: DNS for containers with IPVLAN and bridge attached

[basbebe]

I\m trying to set up two containers via quadlets.
They are connected via an internal, isolated bridge network.

• db container is only attached to the bridge
• service container is attached to the bridge and an IPVLAN

My problems:

At first the service container couldn't reach any IP until I set a metric to the IPVLAN and set no_default_route to the bridge.
But I still can't resolve anything within the service container as long as I'm connected to both networks.
As soon as I connect only to the IPVLAN I can resolve and connect to external hosts.
When being connected only to the bridge I don't seem to be able to resolve the db host's name.

I don't have this problem in a similar setup (bridge not "internal", no IPVLAN)

I'm usind Netavark, Aardvark seems to be running.

Anything I'm missing here or something I should try?

Thanks

[basbebe]

This seems to work after a reboot.

One observation I could make is that when I recreated the internal network, the addresses of aardvark-dns seemed to not update.

sudo netstat -tulpn | rg 53 listet several IPs that did not correlate to an existing network but was missing the newly (re)created network.

What would be the command to restart aardvark-dns / podman networking?

I trief sudo systemctl podman and sudo systemctl podman-restart butthe listening addresses od aardvark-dna were not updated…