Automate the deployment of Red Hat OpenShift Container Platform on IBM zSystems (s390x). Automated User-Provisoned Infrastructure (UPI) setup using Kernel-based Virtual Machine (KVM).
When the Bastion node IPs and OCP node IPs falls differnet subnet zones say 172.23.233.156 be bastion and 172.23.230.64 be master then while setting the rever DNS zone it assume nodes ips also falls under same zone and adds the ip to bastion zone due to which nslookup fails.
To allow this I have added a role multisubnet_reverse_dns which resolves like this.
$ORIGIN 230.23.172.in-addr.arpa.
64 IN PTR master0.ocpz.lnxne.boe.
65 IN PTR master1.ocpz.lnxne.boe.
66 IN PTR master2.ocpz.lnxne.boe.
54 IN PTR worker0.ocpz.lnxne.boe.
68 IN PTR worker1.ocpz.lnxne.boe.
72 IN PTR bootstrap.ocpz.lnxne.boe.
$ORIGIN 233.23.172.in-addr.arpa.
156 IN PTR bastion.ocpz.lnxne.boe.
156 IN PTR api.ocpz.lnxne.boe.
156 IN PTR api-int.ocpz.lnxne.boe.
and the named conf changes like this
zone "23.172.in-addr.arpa" IN {
type master;
file "/var/named/ocpz.rev";
allow-update { any; };
allow-query { any; };
};
When the Bastion node IPs and OCP node IPs falls differnet subnet zones say 172.23.233.156 be bastion and 172.23.230.64 be master then while setting the rever DNS zone it assume nodes ips also falls under same zone and adds the ip to bastion zone due to which nslookup fails. To allow this I have added a role multisubnet_reverse_dns which resolves like this.
and the named conf changes like this