hostnolookup.conf — file containing hostnames or hostname wildcards that should not be resolved to IP addresses using the system IP name server
hostnolookup.conf is a file used by the ovjboss process to determine
whether a hostname should be resolved to an IP address using the system IP name server. The ovjboss process
attempts to match a hostname against each entry in the hostnolookup.conf file before attempting to resolve the
hostname to an IP address. If a match is found, the ovjboss process does not attempt to resolve the
hostname to an IP address using the system IP name server.
Add entries to the file containing one hostname or hostname wildcard. Each entry must be
on a single line. To add comments, place a number sign (#) in front of the comment. That causes
the remainder of the line to be ignored. You can add blank lines to the hostnolookup.conf file.
Use the hostnolookup.conf file if you determine that
a specific hostname (or set of hostnames) cannot be resolved to an IP address using the
systems IP name server.
The administrator must create the hostnolookup.conf
file. It does not exist by default.
If you modify the hostnolookup.conf file while the ovjboss process is running,
use the $NnmInstallDir/support/nmsdnssync.ovpl script to load the updated file.
The nmsdnssync.ovpl script also reloads the ipnolookup.conf file.
The following is an example of a hostnolookup.conf
file:
# A single hostname badsys.mydomain.mycorp.com # An IP wildcard *.baddomain.mycorp.com
In the first example, the system name is bad in some way, causing some DNS servers to respond
with unexpected results. In the second example, there is a domain that cannot be resolved.
Adding these entries to the hostnolookup.conf file stops NNMi from attempting to resolve the
hostnames.