Foreman and SP on the same host with dual network attachement (one private)

Support
21

Our installer does not set A/PTR record for foreman itself, Foreman server should be in unmanaged zone. We assume your DNS record of Foreman FQDN is correctly set before the installation even starts. We don’t check it tho.

22

It’s strange, then since, from a fresh start, where I don’t even have named installed, I get the A record :

# hostname
foreman.dev.cluster.pasteur.fr

# ls -l /var/named
ls: cannot access /var/named: No such file or directory

#  foreman-installer --foreman-proxy-dhcp=true --foreman-proxy-dhcp-interface=eth0 --foreman-proxy-dhcp-managed=true --foreman-proxy-dhcp-subnets="192.168.10.0/24" --foreman-proxy-tftp=true --foreman-proxy-tftp-managed=true --foreman-proxy-dns=true --foreman-proxy-dns-interface=eth0 --foreman-proxy-dns-forwarders="157.99.64.64" --foreman-proxy-dns-managed=true --foreman-proxy-dns-zone=dev.cluster.pasteur.fr --foreman-proxy-bmc=true --enable-foreman-proxy-plugin-ansible --enable-foreman-plugin-ansible --foreman-proxy-dns-reverse=10.168.192.in-addr.arpa
[root@foreman hummel]# grep -i foreman /var/named/dynamic/db.dev.cluster.pasteur.fr 
@ IN SOA foreman.dev.cluster.pasteur.fr. root.dev.cluster.pasteur.fr. (
@ IN NS foreman.dev.cluster.pasteur.fr.
foreman.dev.cluster.pasteur.fr. IN A 192.168.10.10

But no PTR :

@ IN SOA foreman.dev.cluster.pasteur.fr. root.10.168.192.in-addr.arpa. (
@ IN NS foreman.dev.cluster.pasteur.fr.
23

Maybe I am just wrong, @ekohl ?