locked
DNS 2003/2008 MP RRS feed

  • Question

  • Hi,

    I have ran on the following alert at several customers using ws2008 r2 DNS servers, DNS 2008 Troubleshoot AD DS And Restart DNS Server Alert, and with the latest DNS 2003/2008 MP imported into their OpsMgr 2007 R2. This alerts always pop-up after they restarts their DC's after for example performing patch updates. The monitor in OpsMgr 2007 R2 then picks up the event 4013 as it supposed to do but it never goes to healthy again, waiting for any of the events  4400|4522|4523|4524 to appear in the DNS event log. But from what we can see the DNS servers performs alright after system restart.

    i want to have it clarified if it's the actual DNS MP and the minotir itself that's not configured in a way to manage the third healthy event 8to turn green) of if the customers o have problems with their DNS Server configuration?

    I have red many posts about this problem on the net (an example can be found here  http://www.systemcentercentral.com/BlogDetails/tabid/143/IndexID/42081/Default.aspx and Alert: DNS 2008 Troubleshoot AD DS And Restart DNS Server Alert) but I haven't find any clear statement about the monitor trustworthiness in this particular case.

    Thanks in advance

    Regards,

    Richard

    Tuesday, February 15, 2011 9:15 AM

Answers

All replies

  • i think this is just a bug in the monitor. You can report this on connect.microsoft.com.

    But while you are there vote for the complete redesign of the dns mp as there are loads more issues to be addressed in this mp. Most importantly the config churns it causes. https://connect.microsoft.com/OpsMgr/feedback/details/630115/rewrite-dns-entirely

     


    Rob Korving
    http://jama00.wordpress.com/
    • Marked as answer by Yog Li Wednesday, February 23, 2011 3:03 AM
    Wednesday, February 16, 2011 1:57 PM
  • Hi Richard,

    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as "Answered" as the previous steps should be helpful for many similar scenarios.

    In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.

    Thanks,


    Yog Li -- Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, February 23, 2011 3:18 AM
  • Config churn issue should be solved with the new DNS MP 6.0.7000.0 which came out yesterday, check Kevin's write up on it here.

     

    Thursday, February 24, 2011 6:42 PM