Raul Lopez Nevot wrote:
What I need is a procedure that I can use to move the base zone
xxx.yyy.example.com <http://xxx.yyy.example.com>
to BIND, while keeping the six AD zones on the Windows DNS Server.
If I were to define the six AD zones on the Windows DNS Server,
I doubt you can do this with elegance. And, if you have two DNS
servers and one of them is Windows (sure you will have DHCP), your
'reverse zones' will be broken (half of information on each DNS).
You're making several assumptions about the
presence/architecture/configuration of DHCP, its clients and/or servers.
I'll note Barry didn't mention DHCP at all in his original post.
If all of the clients' address assignments are either "static" (no DHCP)
or "manual DHCP" (same address to the same client permanently), or if
the DHCP server, and/or the clients themselves, are authorized to update
both the forward and reverse zones, in response to lease activity, via
TSIG key, GSS-TSIG, or some other authentication regime, then there is
no forward/reverse inconsistency to worry about.
- Kevin
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
