IP (not zone) delegation

[Mark Damrose]

"Kevin Darcy" <kcd at daimlerchrysler.com> wrote in message
news:am86d7$1fn$1 at isrv4.isc.org...
>
>
> My understanding was that the original poster wanted to maintain all data
about
> PCs on the MS-DNS server, including the reverse entries. But, he probably
> *doesn't* want to maintain non-PC data in MS-DNS, and he has mixtures of
PC and
> non-PC devices in both of his (private) /24 ranges. If so, then this is
another
> "split responsibility" issue like so-called "classless in-addr
delegation", and
> the same basic solution applies, i.e. alias individual names where
necessary.
> Sometimes I wish RFC 2317 wasn't written to be targeted so specifically at
> CIDR issues, or even specifically at reverse DNS issues, since aliasing
> techniques are useful for a much wider variety of situations.

I had seen that requirement for the forward zone, but it didn't necessarily
follow that it also applied to the in-addr.  I assumed AD names needed to be
on the MS server rather than all names related to MS clients.  Your answer
makes a lot more sense now.

>
> Or, maybe I have misunderstood the requirements...

Or maybe I did.  The assumptions behind the setup weren't entirely clear.

>
>
> - Kevin
>
>
>