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 only the minimum number of attributes for the
external network:
Object name: hpcpublic
mask=255.255.255.0
mgtifname=eno2
mtu=1500
net=192.168.10.0
usercomment=HPC Public Network
Don't put the gateway, nameserver or domain attributes into the public
network - those would tell xCAT that it should try to manage the network,
rather than just have information about it. I also found that having the
gateway entry in more than one network can cause routing headaches in some
scenarios (I'm not sure if it will cause that problem here).
_______________________________________________________________________
Kevin Keane | Systems Architect | University of San Diego ITS |
kke...@sandiego.edu
Maher Hall, 192 |5998 Alcalá Park | San Diego, CA 92110-2492 | 619.260.6859
*REMEMBER! **No one from IT at USD will ever ask to confirm or supply your
password*.
These messages are an attempt to steal your username and password. Please
do not reply to, click the links within, or open the attachments of these
messages. Delete them!
On Mon, Dec 17, 2018 at 2:11 PM Christian Caruthers <ccaruth...@lenovo.com>
wrote:
> 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=cluster.domain.net
>
>
>
> resolv.conf has the MN as the nameserver:
>
>
>
> domain cluster.domain.net
>
> search cluster.comain.net domain.net
>
> nameserver 172.23.100.10
>
>
>
> … And for the most part, everything works except reverse lookup for IPs
> not managed by this DNS server:
>
>
>
> host mn01
>
> mn01.cluster.domain.net has address 172.23.100.10
>
> host 172.23.100.11
>
> 11.100.23.172.in-addr.arpa domain name pointer n01.cluster.domain.net.
>
>
>
> host compnode01.domain.net
>
> compnode01.domain.net has address of 192.168.100.11
>
>
>
> host 192.168.100.10
>
> host 192.168.100.10.in-addr-arpa. not found: 3(NXDOMAIN)
>
>
>
> host 192.168.100.10 192.168.100.1
>
> Using domain server:
>
> Name: 192.168.100.1
>
> Address: 192.168.100.1#53
>
> Aliases:
>
>
>
> 192.168.100.10.in-addr.arpa domain name pointer mgt01.domain.net
>
>
>
> So, if I give it the remote DNS server, the reverse lookup works. Using
> the xCAT MN, reverse lookup only works for internal IPs.
>
>
>
> Regards,
>
> *Christian Caruthers*
>
> Lenovo Professional Services
>
> Mobile: 757-289-9872
>
>
> _______________________________________________
> xCAT-user mailing list
> xCAT-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xcat-user
>
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
