ipnolookup.conf — file containing IP addresses or IP wildcards that should not be resolved to hostnames using the system IP name server
ipnolookup.conf is a file used by all NNMi processes to
determine whether an IP address should be resolved to a hostname using the system IP name
server. NNMi processes attempt to match an IP address against each entry in the
ipnolookup.conf file before attempting to resolve the
IP address to a hostname. If a match is found, the NNMi process does not attempt to resolve the
IP address to a hostname using the system IP name server.
Add entries to the file containing one IP address or IP wildcard per line. Each entry must be on
a single line. To add comments, place a number sign (#) in front of the comment.
This causes the remainder of the line to be ignored. You can add blank lines to the ipnolookup.conf file.
Use the ipnolookup.conf file when you determine that a
specific IP address (or range of IP addresses) cannot be resolved to a hostname using the
system IP name server.
The administrator must create the ipnolookup.conf file.
It does not exist by default.
If you modify the ipnolookup.conf file while NNMi
processes are running, run the $NnmInstallDir/support/nmsdnssync.ovpl script with no
arguments to load the modifications you made to the ipnolookup.conf file.
The following is an example of a ipnolookup.conf file:
# A single IP address
192.168.1.100
# An IP wildcard
10.*.*.*
# An IP wildcard range
192.168.1.101-255
In the first example, the single IP address could be routed to the Internet because
many web sites use a 192.168.*.* IP address. In the
second example, the IP wildcard range could be NAT addresses. As such, they are not
suitable for communications. In the third example, the IP wildcard range could be a set of
addresses used for some purpose other than the primary IP address.