Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > IP Address Manager (IPAM) > How hostname resolution works in IPAM

How hostname resolution works in IPAM

Table of contents
Created by Brian O'Donovan, last modified by Steven Bansil_ret on Jul 14, 2016

Views: 462 Votes: 3 Revisions: 3

Updated: July 14, 2016

Overview

 

This guide describes how hostname resolution is performed in IPAM.

Environment

All versions of IPAM

Detail

Hostname Resolution in IPAM:

  • When an subnet is scanned, IPAM will try to ping an IP address from range.
  • When IP responds to a ping, IPAM will try to obtain reverse record from DNS server.

 

Hostnames can come from different technologies. We are using a windows function, which is resolving ip address to hostname according the current DNS server settings on the server. It may also get the hostname from other sources:

  • local hosts file
  • local netbios/wins cache
  • remote netbios/wins server query
  • local dns cache
  • remote dns server query
     

If IPAM is not displaying the hostname, verify that the IPAM server can resolve the hostname via Powershell

Launch Powershell on the IPAM server

Run the following commands

$myhost = [System.Net.Dns]::GetHostEntry("10.0.0.1")

$myhost

Replace 10.0.0.1 with the IP Address in question

 

If the server is unable to resolve the hostname from the IP Address IPAM will also be unable to resolve the IP Address.

 

 

Last modified
22:49, 13 Jul 2016

Tags

Classifications

Public