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.
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.
But how does that address my issue? The nslookup and whois explorer commands use an external service to do their look ups.
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
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.
