Mehmet -It sounds like what you're looking for is more of a generic "Verify DNS is synchronized" probe as opposed to the current DNS probes which fire a query at a single NS and make sure the response is what's expected. Intermapper's design isn't really geared for that since each probe asks a question of it's specific device (this test by its nature needs to query N devices - all the listed nameservers)
This is a pretty common problem though, common enough that it's pobably worth having a probe for. Since it gives me an excuse to play with the new 5.2 command-line probe bits I came up with the attached: Just stick it on a device that's an authoritative NS for the zone & make sure the domain name (zone) is set correctly in the probe parameters.
Caveats:- Any difference in the SOA is an error (your SOAs should match exactly anyway or you're doing DNS wrong :)
- Only reports the first SOA mismatch it finds - Only works on InterMapper 5.2 (uses the <tool:> section)- Probably only works on Unix hosts (Tested on FreeBSD, Probably works on Mac/Linux without changes).
- May cause REALLY LONG reason strings in your status window(No other way to display the script output / list of checked servers - ?)
Improvements welcome. This is a pretty ghetto 10 minute implementation...
-MG
net.bsd-box.cmdline.dns.soa
Description: Binary data
On Jan 11, 2010, at 12:56 AM, Mehmet Akcin wrote:
Bill,I am trying to achieve following, have intermapper two different digs , one - dig @master-dns-server-address . SOA grab the serial "2009081901" and other dig @slave-dns-server-address . SOA and grab the serial from there, if they match everything is great. If the serial # in master > slave --- there is mismatch and for some reason the slave dns server is not updating in timely manner.I believe this would have been an awesome feature if Intermapper could provide as a feature , mis-matching SOA on master and slave (s) is a very important thing that needs monitoring for many .insert your peer-pressuring supportive words here <<< :)cheers Mehmet On Jan 10, 2010, at 3:12 PM, William Fisher wrote:On 1/9/10 3:12 PM, Mehmet Akcin wrote:I am trying to build a custom DNS Probe which would check the SOA for domain "example.com" on server1 and if matches with the SOA for domain "example.com" in server2 , it would be a happy probe:)The editable content of the DNS probes is in the BuiltInProbes.zip file in the "InterMapper Settings/Probes" directory. However, when you look at the content of the DNS probes, you are going to see that there are only two sections: header and parameters, and the probe's type is "built-in". The DNS probes are implemented in C++ code that is linked within InterMapper itself. There is no way to write a custom UDP probe at this time.any ideas if anyone has done something with SOA's before?I see the DNS related probes dont contain SOA but other record types such as A/MX etc, is there a way to get the editable format of the DNS Probe to play and modify... this is if acceptable...I am interested in what you are trying to do. To make sure I understand, please describe the logic of the probe. Given a raw SOA response of the following format, what do you want to check? (the fields are domain, email, serial number, refresh, update retry, expiry, minimum)ns1.example.com. dns.example.com. 2009081901 3600 900 864000 43200 Thanks, -- Bill Fisher Dartware, LLC ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [email protected]____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [email protected]
