Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > DNS entry is unavailable on a monitored node

DNS entry is unavailable on a monitored node

Updated June 29, 2017


A DNS entry is not available and is displayed as a blank entry on a node.


  • All NPM versions
  • All SAM versions
  • All UDT versions


The reverse DNS is unavailable for the IP address on the DNS server where the Orion server is configured to query on the primary NIC.


  1. Establish a remote connection to the Orion server.
  2. Open a command prompt and run the following command:
    nslookup [IP address]

If no response is received, this means that Orion is unable to determine the DNS.

Consult with the DNS server administrator as there may be no PTR record or a badly configured record is present.


Last modified