There already is support in dns.monitor for recursive server testing. (I wrote the code....)
try "dns.monitor -caching_only -query www.yahoo.com:A -query google.com:MX <servername>" -David On Tue, Nov 3, 2009 at 4:11 PM, Nathan Gibbs <nat...@cmpublishers.com> wrote: > * Kastus Shchuka wrote: >> On Tue, Nov 03, 2009 at 12:24:33PM -0500, Nathan Gibbs wrote: >>> Isn't a resolver part of the OS libraries that do DNS lookups, not a >>> network service that can be checked. >> >> Mike probably used "resolver" meaning "recursive/caching server" > > Yeah, your right there. > >> There is no sense in monitoring resolver libraries. > > My point exactly. At least, that was what I was trying to say. > :-) > >> Yo may want to >> look at http://cr.yp.to/djbdns/separation.html for explanation. >> >>> dns.monitor -caching_only record:TXT:result >>> >>> should be able to do it, but doesn't appear to work like the >>> instructions say. >> >> There are too many aspects involved in recursive name resolution and there is >> no easy way (or sense) to monitor all of them. >> > > Right. > >> dns.monitor is only proving that all authoritative DNS servers serve the >> same zone information. They do not check if published zone is correct, >> though. >> >> One possible way to monitor recursive/caching server would be to >> resolve a name coming from a known good authritative server. >> It's fairly easy to script and convert into a monitor. > > Yeah, > A few mod's to dns.monitor would make that work. > I don't plan on doing it this year, maybe next. > > > -- > Sincerely, > > Nathan Gibbs > > Systems Administrator > Christ Media > http://www.cmpublishers.com > > > > _______________________________________________ > mon mailing list > mon@linux.kernel.org > http://linux.kernel.org/mailman/listinfo/mon > > _______________________________________________ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
