|
Your desire is a bit unclear. Regardless, stop thinking about rendom.
;-) My guess is that you want to consolidate DNS domains currently hosted on
BIND to W2K3 DC/DNS servers. This is a fairly trivial exercise from a server
perspective. The following basic steps are required: 1. Configure
the BIND server to allow secondary zone transfers to your favorite W2K3 DC/DNS
server. 2. Configure
the W2K3 DC/DNS server to host a secondary zone for the zone configured in (1)
above. 3. Modify
the delegation for the zone in the “parent” zone to include the
W2K3 DC/DNS server. 4. Modify
the configuration of the zone on the W2K3 DC/DNS server marking it as AD
Integrated. 5. Wait
for replication of the zone to complete. 6. Modify
the delegation for the zone in the “parent” zone to include ALL the
W2K3 DC/DNS servers that will host a copy of the zone. 7. Remove
the zone from the BIND server. At this point the W2K3 DNS server will have a copy of the zone –
other options to complete this portion do exist such as forklifting the zone
files which in your case (with many zones) could be much more acceptable from
an administrative perspective. While the above will work in many environments there could be factors
in your infrastructure that could be problematic such as how DNS is interconnected
throughout the organization, where clients point to for Primary/Secondary,
etc. One way to work around these potential issues is to reconfigure the BIND
server with a secondary zone (for each moved zone) until you can properly
resolve all the issues associated with the move. HTH Aric From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott McIntosh Our company has the following DNS architecture (this is somewhat
oversimplified but illustrates the point): |
- RE: [ActiveDir] Bernard, Aric
- [ActiveDir] Doug Ferguson
- Re: [ActiveDir] Brett Shirley
- [ActiveDir] AD printer Auditing and logging Jason Yaremchuk
