DNS PTR records not being used when provisioning
Description
Environment
Debian server 8
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
Bill Seymour March 29, 2016 at 12:12 PM
In Home;Admin;Discovery;Modify Configuration I have Include Ranges set to match the local subnet. Discovery finds the workstations on the subnet but enters them into the Nodes database as IP addresses instead of by their machine name.
David Hustace March 18, 2016 at 7:33 AM
When you say "workstations are entered by IP address", are you saying that you are creating newSuspect events from the UI or from the command line using the IP address? We need to better understand how you are provisioning the nodes into OpenNMS.
When provisioning nodes in an Active Directory environment, workstations are entered by IP address instead of by the name returned via a DNS request. For example: I have a workstation at a specific IP address (nslookup returned the workstation address when requesting using the machine name). Here is the results of a request for the machine name and for the IP address on the Debian server:
billsey@SRV-NMS:/etc/opennms$ nslookup itsupport-pc
Server: 192.168.17.4
Address: 192.168.17.4#53
Name: itsupport-pc.gsslinc.local
Address: 192.168.17.244
billsey@SRV-NMS:/etc/opennms$ nslookup 192.168.17.244
Server: 192.168.17.4
Address: 192.168.17.4#53
244.17.168.192.in-addr.arpa name = itsupport-pc.gsslinc.local.
Yet the node is shown in OpenNMS as '192.168.17.244', not itsupport-pc or itsupport-pc.gsslinc.local. Turning on debug logging for provisiond does not show any attempts to use DNS for naming, only attempts to check for DNS servers at the address.