Chad,
I'll reply to this as a clarification, as I'm not realy sure what you're
after.
Integrated DNS (i.e. Active Directory Integrated - be that in the AD
directly, or through a replicated application partition) CAN support both
Stub Zones and Conditional Forwarding - and there are good reasons why you
would want to use them. However, the reasons are basically the same as to
why you would want to use them in a Standard Pri/Sec config as well.
Firstly, remember that DNS information is Domain-based. Meaning that if I
have a domain foo.com, records for foo.com will not be replicated to
a.foo.com, nor will records from a.foo.com be replicated to foo.com. So,
stub zones play a role if I need information about another domain (NS, SOA,
A) and the information can maintained in the integrated DNS.
Effectively, same thing goes with the Conditional Forwarding. If I want to
forward all requests for a.foo.com to NS at IP 12.13.14.15, then there is
nothing that will prevent me from creating the conditional rules in the
integrated model.
Both models (Standard and AD Integrated) can provide these functions. It's
up to your needs and requirements if these functions make sense.
