Description of problem:

• `satellite-installer --enable-iopplugin` in Satellite 6.18 fails to initialize the containers showing next error message.

  2026-01-28 08:57:54 [ERROR ] [configure] Jan 28 08:57:54 satellite.example.com iop-core-kafka[50484]: Error: netavark: error while applying dns entries: IO error: aardvark-dns failed to start: Error from child process
  2026-01-28 08:57:54 [ERROR ] [configure] Jan 28 08:57:54 satellite.example.com iop-core-kafka[50484]: Error starting server failed to bind udp listener on 10.130.xx.xx:53: IO error: Address already in use (os error 98)
  2026-01-28 08:57:54 [ERROR ] [configure] Jan 28 08:57:54 satellite.example.com systemd[1]: iop-core-kafka.service: Main process exited, code=exited, status=126/n/a 

  How reproducible:

• Always

Is this issue a regression from an earlier version:

• No

Steps to Reproduce:

• Enable dns in Satellite server.

satellite-installer --foreman-proxy-dns true \
            --foreman-proxy-dns-managed true \
            --foreman-proxy-dns-forwarders "10.38.5.26" \
            --foreman-proxy-dns-interface "ens224" \
            --foreman-proxy-dns-reverse "1.168.192.in-addr.arpa" \
            --foreman-proxy-dns-zone "example.com" \
 

• Enable `iop` plugin.

satellite-installer --enable-iop 

Actual behavior:

• Containers creation fails because `netavark` is not able to use port 53.

Workaround:

•  The Root Cause is that `satellite-installer` configures named to listen on all available addresses.
• AFAIK there is no installer parameter to set the `listen-to` named option.
• Temporal workaround, until next Satellite update is to modify the used template to restrict the `listen-to` addresses. 

echo "listen-on port 53 { 127.0.0.1; 192.168.xx.xx; };" >> /usr/share/foreman-installer/modules/dns/templates/options.conf.erb