How to verify that dns_bind_port is working?

[MadSpindel]

I've a Adguard Home DNS pod using port 53. As a consequence, internal DNS between pods is not working. I've changed the dns_bind_port to 54 in /etc/containers/containers.conf. My network says dns_enabled = True. Still, it uses the Adguard Home DNS pod as DNS.

What am I missing here? How can I verify that the pods are trying to use port 54 for DNS queries?

{
          "name": "podman-default-kube-network",
          "id": "0f0781dd414e21b6be455407b6eb3142156a82586e03c69304f8756c7e6f43ac",
          "driver": "bridge",
          "network_interface": "podman1",
          "created": "2023-07-28T00:00:38.763733573Z",
          "subnets": [
               {
                    "subnet": "10.89.0.0/24",
                    "gateway": "10.89.0.1"
               }
          ],
          "ipv6_enabled": false,
          "internal": false,
          "dns_enabled": true,
          "ipam_options": {
               "driver": "host-local"
          }
     }

[Luap99]

$ cat /etc/containers/containers.conf 
[network]
dns_bind_port = 54
$ sudo podman network create t1
t1
$ sudo podman run -d --name c1 --network t1  alpine sleep inf
b5a02f9b7b20393d34612f5087e0b216f95ef4c6246ee2fed8581312c63d48e9
$ sudo ss -ulpn | grep 54
UNCONN 0      0          127.0.0.54:53         0.0.0.0:*    users:(("systemd-resolve",pid=1613,fd=18))
UNCONN 0      0           10.89.0.1:54         0.0.0.0:*    users:(("aardvark-dns",pid=45525,fd=9))
$ ps aux | grep aardvark-dns
root       45525  0.0  0.0 1683260 2948 ?        Ssl  13:38   0:00 /usr/libexec/podman/aardvark-dns --config /run/containers/networks/aardvark-dns -p 54 run
pholzing   45885  0.0  0.0 222540  2560 pts/3    S+   13:39   0:00 grep --color=auto aardvark-dns
$ sudo iptables -t nat -S NETAVARK-HOSTPORT-DNAT
-N NETAVARK-HOSTPORT-DNAT
-A NETAVARK-HOSTPORT-DNAT -d 10.89.0.1/32 -p udp -m udp --dport 53 -j DNAT --to-destination 10.89.0.1:54
$ sudo podman run --rm --network t1  alpine nslookup c1
Server:		10.89.0.1
Address:	10.89.0.1:53

Non-authoritative answer:
Name:	c1.dns.podman
Address: 10.89.0.2

Non-authoritative answer:

Note in order for the dns_bind_port setting to take effect you must set it before the containers are started. If aardvark-dns was started before it it will listen on the wrong port. So you should stop all containers before changing this (make sure no aardvark-dns process is still listening), then start the containers again. This will bring up aardvark-dns on the right port.