I just had to deal with a similar issue. Try the following:
- Fill out each network in the networks table, including domain name.
Don’t worry about nameservers or gateway unless there is are external resources
that should be used. NOTE defining an external nameserver in networks table
will cause makedns to ignore any IPs in that subnet.
- Define hpcmn-test as an unmanaged node in the cluster (nodeadd
hpcmn-test groups=__Unmanaged or something similar)
- Define its primary interface (the one whose domain matches
site.domain value) in hosts.node/hosts.ip (this should also be what was deinfed
in nodelist above)
- Define all other interfaces in hosts.otherinterfaces with fqdn. For
example:
“hpcmn-test”,”1.2.3.4”,,”hpctest.compute.sabre.kkeane.sandiego.edu:2.3.4.5,hpcmn-test.imm.sabre.kkeane.sandiego.edu:3.4.5.6”,,,,
The domain names listed for each IP in hosts should match the networks.domain
entry for each respective subnet.
Regards,
Christian Caruthers
Lenovo Professional Services
Mobile: 757-289-9872
From: Kevin Keane [mailto:kke...@sandiego.edu]
Sent: Tuesday, October 31, 2017 4:21 PM
To: xCAT Users Mailing list <xcat-user@lists.sourceforge.net>
Subject: [xcat-user] makedns-generated zones and their NS record
I have a management node with three NICs, and want to use makedns to generate
the DNS configuration.
My management node has three names, corresponding to the three NICs:
eth0:
hpcmn-test.compute.sabre.kkeane.sandiego.edu<http://hpcmn-test.compute.sabre.kkeane.sandiego.edu>
eth1: hpcmn-test.kkeane.sandiego.edu<http://hpcmn-test.kkeane.sandiego.edu>
eth2:
hpcmn-test.imm.sabre.kkeane.sandiego.edu<http://hpcmn-test.imm.sabre.kkeane.sandiego.edu>
hostname -f returns
hpcmn-test.kkeane.sandiego.edu<http://hpcmn-test.kkeane.sandiego.edu> (which is
name by which my management node will be known on our public network).
I have the DNS server listening only on eth2. Consequently, the zones in the
DNS server should have the corresponding name server
hpcmn-test.imm.sabre.kkeane.sandiego.edu<http://hpcmn-test.imm.sabre.kkeane.sandiego.edu>.
However, the zones generated by makedns -n instead use the
hpcmn-test.kkeane.sandiego.edu<http://hpcmn-test.kkeane.sandiego.edu> name.
$TTL 86400
@ IN SOA hpcmn-test.kkeane.sandiego.edu<http://hpcmn-test.kkeane.sandiego.edu>.
root.hpcmn-test.kkeane.sandiego.edu<http://root.hpcmn-test.kkeane.sandiego.edu>.
( 2017103100 10800 3600 604800 86400 )
IN NS hpcmn-test.kkeane.sandiego.edu<http://hpcmn-test.kkeane.sandiego.edu>.
This wreaks havoc with future calls to makedns; updates will time out because
the DNS server is not listening at the IP address that corresponds to this name
(and in fact, makehosts doesn't even put this name into /etc/hosts)
How can I get makedns to generate zones with an NS record that points to
hpcmn-test.imm.sabre.kkeane.sandiego.edu<http://hpcmn-test.imm.sabre.kkeane.sandiego.edu>
?
Thanks!
--
_______________________________________________________________________
Kevin Keane | Systems Architect | University of San Diego ITS |
kke...@sandiego.edu<mailto:kke...@sandiego.edu>
Maher Hall, 192 |5998 Alcalá Park | San Diego, CA 92110-2492 |
619.260.6859<tel:%28619%29%20260-2298>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
