.Red Hat Lightspeed might fail on Satellite servers with managed DNS When the `named` service is already running on a Satellite server, the `aardvark-dns` service, which is required for running containers, fails to start. This is caused by a conflict between `named` and `podman` configurations for IPv4 connections. As a consequence, Red Hat Lightspeed installations might fail on Satellite servers configured for managed DNS. To work around this problem, perform the following steps: . Set managed DNS in `satellite-installer` to `unmanaged`: + ---- # satellite-installer --foreman-proxy-dns-managed=false ----   . Configure your Satellite server to only listen on the local IP addresses by adding the following content to the `/etc/named/options.conf` file: + ---- listen-on-v6 { fd00:4::25; }; listen-on { 192.168.4.25; }; ---- . Restart the `named` service. . You can verify that the configuration works by checking that the DNS service is listening on port `53`: + ---- [ root@satellite6 :/root]# netstat -tulpn| grep 53 tcp 0 0 10.130.0.1:53 0.0.0.0:* LISTEN 2199/aardvark-dns tcp 0 0 192.168.122.1:53 0.0.0.0:* LISTEN 2252/dnsmasq tcp 0 0 192.168.4.25:53 0.0.0.0:* LISTEN 1016/named tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 1016/named tcp6 0 0 fd00:4::25:53 :::* LISTEN 1016/named ----