How do folks check DNS for MS AD Domains (SVR records ??) ?

[Stanley Hopcroft]

Dear Ladies and Gentlemen,

Your comments on checking that a DNS is able to resolve the names used 
by AD logon are very welcome.

Being very ignorant, it seems to me that what is required is to be able 
resolve the SVR resource records that MS domain controllers register in 
a Dynamic DNS.

These records include some of these SVR records at least :-

. _ldap._tcp.<DNSDomainName>

. _ldap._tcp.pdc._ms-dcs.<DNSDomainName>

Of course, this may well be a _dumb_ idea since most name resolution 
tools do not seem to handle SVR records.

(OTOH, the CPAN module Net::DNS may be able to resolve SVR records).

To sum up, the list and certainly I will be very grateful for being 
informed on how folks use Nagios to check MS AD name resolution and if 
in fact it is possible to use check_dns for this purpose.

Thank you,

Yours sincerely.


-- 
------------------------------------------------------------------------
Stanley Hopcroft
------------------------------------------------------------------------

'...No man is an island, entire of itself; every man is a piece of the
continent, a part of the main. If a clod be washed away by the sea,
Europe is the less, as well as if a promontory were, as well as if a
manor of thy friend's or of thine own were. Any man's death diminishes
me, because I am involved in mankind; and therefore never send to know
for whom the bell tolls; it tolls for thee...'

from Meditation 17, J Donne.


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null