I think your problem may be that xCAT took control of the 192.168.100.0
subnet, when you really just meant to inform xCAT about the network's
existence. As a result, DNS queries are not forwarded to the 192.168.100.1
DNS server that actually does know about this zone.
In our system, I have defined
Hello Christian Caruthers,
Thanks for your mail. The feature you asked is not provide by xCAT by default.
xCAT only configured BIND 9 to resolve the hostnames and IPs managed in xCAT
cluster.
In your question, IPv4 address 172.23.100.10 and 192.168.100.10 both belong to
Address Allocation for
Running Version 2.14.1.lenovo2 on RHEL 7.4.
I have the following "external" network defined:
Object name: DLS
domain=domain.net
gateway=192.168.100.254
mask=255.255.255.0
mgtifname=eno1
nameservers=192.168.100.1
net=192.168.100.0
site.forwarders = 192.168.100.1
site.domain
