Opmantek software works much better if hostnames can be resolved; however some customer environments do not have DNS servers. Opmantek software can function without DNS, but it functions much better with it. With this in mind we'd like to suggest running BIND (Berkly Internet Name Domain) on the NMIS Primary server if local DNS servers are not available. This Primary server can then be the DNS server for all other NMIS servers in the customer environment.
This article will assume the NMIS server OS is CentOS 6 as this is the most widely deployed OS for our customer base.
Decisions & Actions Prior to Installation
- Static IP address on the server
- This example: 192.168.10.68
- Choose and configure the server hostname
- This example: opmantek
- Choose domain name
- This example: nmis.local
Installation & Configuration
/etc/hosts should reflect the proper IP address and hostname of the server. For example:
Using YUM install bind.
There are three things we should evaluate in /etc/named.conf
- Listen on the static IP address
- If IPv6 is not used, disable it.
- Define 'allow-query' subnets, or disable. These are addresses that are allowed to query this server for name resolution.
The syntax is very critical here.
The script below will automatically create the zone file based on input from the operator (IP address, hostname & domain name). It will create a DNS entry for every node provisioned in NMIS. If a node is added to NMIS simply re-run the script and restart the named service.
Update /etc/named.conf To Use New Zone File
We need to update /etc/named.conf to use the newly created zone file. Add an entry referencing it such as this:
Enable and Start named
/etc/reslov.conf should only contain the following.
- search <domain name>
- nameserver <IP Address>
Now we should be able to ping any NMIS node like so: