We are in a very small office, maybe a dozen machines pointed to a Windows 2012 R2 DC for DNS, probably less than 6 actually joined to the domain.

And every since I've started playing with PRTG its said the DNS response time on our DC was "unusual for this hour of the week". 24 hours a day, 7 days a week. The server has plenty of resources and literally does nothing but run AD and DNS.

Anyone ever run into this and have a solution?

Fair warning. I'm just learning PRTG and having to do it on my own as my boss doesn't think it's worth while so forgive me if I have stupid questions. :)

Article Comments

Hello jcramseyiii,

Thank you very much for your kb post.

We need to take a further look at the affected sensor, therefore please open a support ticket or feel free to contact us via email to support@paessler.com.

Please provide us with:
1.) a screenshot of the sensor's "Overview" tab
2.) a screenshot of the sensor's "Log" tab
3.) the sensor's configuration report (which can be generated within the sensor's "Settings" tab, using the small printer icon on the gray bar at the bottom of the page from where the report can be generated, simply print/save this as PDF file)

Please make sure to capture the whole PRTG user interface (neither cropped nor resized) in any screenshot and attach them as email file attachment.

Best regards,
Sebastian


Jul, 2017 - Permalink