Hi, I have installed controller-0 and bootstrap was failed at 'Download images and push to local registry'. I noticed that, dns resolution is failing in the controller but not in the host. controller-0:~$ dig docker.io ; <<>> DiG 9.9.4-RedHat-9.9.4-72.el7 <<>> docker.io ;; global options: +cmd ;; connection timed out; no servers could be reached controller-0:~$ ping quay.io PING quay.io (3.233.133.41) 56(84) bytes of data. --- quay.io ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2054ms I can ping from the controller. I have added following entries to iptables but no luck. sudo iptables -A OUTPUT -p udp -d 8.8.4.4,8.8.8.8 --dport 53 -m state --state NEW,ESTABLISHED -j ACCEPT sudo iptables -A INPUT -p udp -s 8.8.4.4,8.8.8.8 --sport 53 -m state --state ESTABLISHED -j ACCEPT sudo iptables -A OUTPUT -p tcp -d 8.8.4.4,8.8.8.8 --dport 53 -m state --state NEW,ESTABLISHED -j ACCEPT sudo iptables -A INPUT -p tcp -s 8.8.4.4,8.8.8.8 --sport 53 -m state --state ESTABLISHED -j ACCEPT I am not sure if my network configuration is correct. controller-0:~$ ip route list default via 10.10.10.1 dev ens3 10.10.10.0/24 dev ens3 proto kernel scope link src 10.10.10.3 169.254.0.0/16 dev eth1000 scope link metric 1002 169.254.0.0/16 dev eth1001 scope link metric 1003 169.254.0.0/16 dev ens3 scope link metric 1004 169.254.0.0/16 dev ens4 scope link metric 1005 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown Following is my local routing configuration and host IP is 192.168.10.100. $ ip route list default via 192.168.172.3 dev eno1 proto static metric 100 10.10.10.0/24 dev stxbr1 proto kernel scope link src 10.10.10.1 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 192.168.10.0/24 dev eno1 proto kernel scope link src 192.168.10.100 metric 100 IP -a results available at http://paste.openstack.org/show/802048/