Win2k, bind on unix, and reverse lookup sanity.

[Kevin Darcy]

Jason Price wrote:

> Short version: Are there some docs/good ideas/best practices for how to
> share reverse lookup duty between bind and win2k's ActiveDirectory in a
> shared, private IP range?
>
> We have a large mixed environment, and we're adding win2k/AD to the
> mix.  I've got forward lookups knocked out (just carve them a subdomain,
> and delatate it away to them.  They in turn forward requests back to
> bind for internet and 'legacy' lookups.)
>
> We all need to live in the same ip network.  What's a good way to
> cleanly deal with reverse lookups?  Win2k/XP clients need reverse
> lookups (hosted by win2k!) to login to the AD tree.  Unix hosts need
> reverse lookups so that they can be backed up (requirement of veritas
> netbackup)
>
> We all live in a 10.* network, subnetted for for various tasks (wan
> sites, etc).  Should I set up a central authority for 10.*, and delegate
> the various subdomains that win2k will need to play in?

Yup.

> Do I just tell bind "you have control of these (10.x.y.z) reverse
> lookups, look over there for those (10.a.b.c)"?  If so, how do I do
> that?  (aka: 'In general, you need to follow your hints, but for this
> exception, go to this other server')

If the exceptions are delegated properly, this should happen automatically.


- Kevin