Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > No DNS entries exist for hostname

No DNS entries exist for hostname

Updated August 3rd, 2018

Overview

The following error appears when trying to edit an interface for any device that is assigned to an additional poller:

There was an error communicating with the Orion server. No DNS entries exist for hostname.example.ex.

 

OrionWeb.log

2017-03-30 15:29:54,745 [209] (610) WARN  SolarWinds.Orion.Core.Common.DALs.ModuleGlobalDAL - (null)  Engine with ID=2 was not found.

 

InformationServiceV3.log

2017-03-30 15:20:48,682 [91] ERROR SolarWinds.Data.Providers.Orion.ModuleGlobalTable - (null) (null)     Error connecting to Engine #2 Hostname Additional at 10.XX.XX.X. System.ServiceModel.EndpointNotFoundException: No DNS entries exist for host Hostname. ---> System.Net.Sockets.SocketException: No such host is known
   at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
   at System.Net.Dns.GetHostEntry(String hostNameOrAddress)
   at System.ServiceModel.Channels.DnsCache.Resolve(Uri uri)
   --- End of inner exception stack trace --- 

Environment

NPM version 12

Cause 

Additional pollers are not able to do a forward lookup for the hostname. 

Resolution


Its important to check if NSLOOKUP works for both short hostname and long hostname.
For example.

  • sup-aus-malm-02
  • sup-aus-malm-02.swdev.local

 

  1. Log in into the additional poller and open a command prompt. 
  2. Run nslookup:

    Example output for valid forward lookup:

    nslookup sup-aus-malm-02.swdev.local

    Server:  aus-dev-dc-02.swdev.local
    Address:  10.110.108.11

    Name:    sup-aus-malm-02.swdev.local
    Address:  10.110.6.169

     

    Example output for incorrect lookup:

    nslookup sup-aus-malm
    Server:  aus-dev-dc-02.swdev.local
    Address:  10.110.108.11

     

    *** aus-dev-dc-02.swdev.local can't find sup-aus-malm: Non-existent domain

  3. Change the poller to primary poller to test.
  4. Server team will need to correct the DNS issue for forward lookup. 
    Alternatively can bypass DNS Server by adding a HOSTS file entry for both short hostname and long host name on any of your Orion Servers.

 

 

 

Last modified

Tags

Classifications

Public