A DNS error was reported on the Console and NSLookup was failing but the Agent status in the Monitor was fine. It was suggested to check the Data Sources tab in the Monitor to see when it first connected to the device, to see if there was an earlier time when there was a DNS entry. The issue was resolved later.
Read the entire ‘Troubleshooting DNS Error on ControlUp Console and Monitor’ thread below:
Getting a DNS error on the Console but no issue with the agent status in the monitor. The console and monitor were running on the same Server. is there a difference between how the console and the monitor can communicate with the agents other than port. NSLookup fails as well
Hey @member The monitor and console will connect to the agents using the same port – 40705. If you are getting NSLookup issues, then I suspect that the monitor must have connected to the agent at an earlier time when there was a DNS entry for the system. You can check when the monitor connected by going to your monitor status, then selecting the Data Sources tab. Expand the Status column to about 3x it’s current size before navigating down the directory. Once done, navigate to one of those machines and then click on the Show link to see when the monitor connected to that device or if there is an error here as well.
@member thanks i’ll be looking at this more today
went to check today and look into it more issue was gone
Continue reading and comment on the thread ‘Error: “No DNS entries exist for host” on ControlUp Console’. Not a member? Join Here!
Categories: All Archives, ControlUp for VDI