Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Internal hostname lookup functionality

The current nslookup functionality uses external services and cannot see or resolve internal system names. We are running "ping- a [ip]" commands by hand to get name resolution on internal systems.

Find more posts tagged with

security_information_and_event_manangement

siem

hipaa

Accepted answers

All comments

FormerMember

Hi rduvall,

Have you configured your LEM Manager network configuration using a static configuration? It is key to ensure you complete the network configuration and provide at least one DNS server for your local network. You can do this from the command line.

rduvall

But how does that address my issue? The nslookup and whois explorer commands use an external service to do their look ups.

FormerMember

Hi,

I see your point for WhoIS, but NSLookup and Traceroute tools use your configured DNS Server on the LEM Manager. I have validated this on my own installation, by querying several devices on my local domain and domain names external to my organisation and they return the expected results. Can you confirm that you have your LEM manager configured to use the correct DNS servers (i.e. a local DNS server with a forward lookup zone in your network).

Here is a Traceroute to bbc.co.uk

External NSLookup

Lookup to a sever on my training LAN

Traceroute to a server on my Training LAN

rduvall

Is there a way to see the network configuration without changing it? The only thing I can find is the netconfig command, which doesn’t show you the current settings.

FormerMember

Hi,

Yes there is.

1) Open the Console in Hyper-V/ vSphere client or SSH to the appliance and login to the cmc account (view advanced configuration if from the former)

cmc> appliance

cmc::acm# viewnetconfig

Would you like to view the (b)rief network configuration or (a)dvanced? <B/a> a

Look for:

DNS Server Information:

search xxxx.local

nameserver 192.168.xxx.

Locally Configured Hosts:

127.0.0.1 localhost localhost.localdomain db

192.168.xxx.xxx lemhostname

Take a note of every setting. If it is not correct, you should take a note of it then re-run the netconfig command and specify the settings (you will need to set everything again).

rduvall

Everything is correct.

I still get “agent not found” errors when I attempt an nslookup.