Skip to main content

mom: monitoring dns synthetically...

update: this script has been rewritten.  please refer to this post.

 

background. let me start off by posing a question. have you looked at the dns mp? look closely. there are no synthetic tests. why is it that management packs like these are service-centric?

my dns service hums right along... yet problems exist.  i'm not going to expatiate on the necessity of needing transaction-based monitoring. there are whole companies built around this philosophy. it does seem troubling to me though that the cornerstone of active directory is a healthy dns... yet the dns mp contains no such necessary rule. anyway, enough about that.

foreground. i wrote a script to monitor dns. it doesn't monitor the health or catch events. you've already got all that. it simply runs a nslookup command for a list of hostnames and returns errors, if there are any. it lacks any elegance or sophistication (not that you're used to that in my scripts). maybe you noticed. maybe you didn't.

i stated above that it issues nslookup commands. you may be thinking, why nslookup when you could query records through wmi? well, simple... that'd be too easy. seriously, the reason is that there was a time in the past where the dns service hung (no, mom didn't catch that either). i couldn't query anything with nslookup. however, issuing commands against wmi still continued to work. hmmmm. i guess for that reason i'm a little leery about using wmi. besides, using nslookup seems like it more closely resembles what someone might be doing. i would prefer dig, but nslookup seems quite ubiquitous in the windows world. the script has two parameters you'll need to setup:

  • HostNames - accepts a comma-delimited list of hosts to query
  • LogSuccessEvent - boolean value to log on success
should be self-explanatory. "DNS Synthetic Script" is the source. these are the event id values to pick up in any cooresponding alert rule:
  • 41000 - no hostnames defined
  • 41001 - lookup failed for
  • 41002 - successfully looked up
get the script here: i've posted the script at the other two locations. sooner or later they'll post them.

Comments

  1. Now available at MOMResources.org

    http://momresources.org/momscripts/mom_dns_lookup.txt

    Thanks Marcus!

    ReplyDelete

Post a Comment

Popular posts from this blog

how to retrieve your ip address with powershell...

update: this is how it’s performed in powershell v3 as demonstrated here.(get-netadapter | get-netipaddress | ? addressfamily -eq'IPv4').ipaddress update: this is by far the easiest.PS C:\temp> (gwmi Win32_NetworkAdapterConfiguration | ? { $_.IPAddress -ne $null }).ipaddress
192.168.1.101
are you laughing yet?  i know you probably find this topic amusing.  it's really interesting though.  whenever you get over it, i'll do this in the standard cmd.exe interpreter and then in powershell to show you what kind of coolness powershell does.done?  okay, good.  this is an interpretation of a demo that bob wells did at our smug meeting.  hope you like it.i should tell you, it's not as simple as the title would lead you to believe.  i like doing that little slight-of-hand thing since it gives the impression that i'm painting a very easy target on my back for your criticism (though it's probably true in other ways)!  the idea is that we want to retrieve just the ip ad…

understanding the “ad op master is inconsistent” alert

i use the term “understanding” loosely.  this is by far no definitive guide on this particular alert, just a few things i have picked up in my attempt to understand it.let’s look at the context of the alert:The Domain Controller's Op Master is inconsitent. See additional alerts for details.
first of all, it gives very little information.  the only particularly useful detail is that it indicates which server is having the issue.  other than that, just a spelling error as there are no additional critical alerts to look at for details.this rule, as you know, comes from a sealed mp.  therefore, we can’t modify anything in it except the overrides.  the couple i’ve tinkered with are:interval (sec) log success event to begin with, interval (sec) is just set way too high.  the default is 60 seconds.  why on earth would anyone want to know that your op master consistency may be off, every minute?  actually, i could think of a few reasons, but really, it’s overkill.  the way the script works…

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point. even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch.I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.DETECTIONstatus messagestake a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough material to …