question about using dynamic dns and dynamic dhcp and replication of data

[Paul E.]

Hi, i wonder if anybody can help, i have a question regards using dynamic
dns and dynamic dhcp, instead of using wins. I have recently setup a test
win2k server and started playing around with dynamic dns (integrated ad dns
zones as well) and dynamic dhcp, this all seemed great and worked a treat,
but i then started wondering how this would work at the other sites i have.

At the moment im running windows NT 4.0 servers across WAN links to 4 other
sites, they are all currently using wins and the wins databases are
replicating to our central site, all hunky dorey i thought, but i then
started thinking about how dynamic dns may do this instead when i move to
win2k and came across the problem that you cannot have multiple pri dns
zones with the same name, you can only have secondary zones, but these are
read only, so how would the dc's at the remote sites write to the primary
dns zone?.

The only way i can see this working is if the remote sites dont have a dns
server and instead all point to my central site which hosts the pri dns
zone, but surely this would mean an increase in traffic?

If anybody can clarify this for me then i would be very grateful.

A slightly worried and confused techy! ,

Paul.

 

[Moreno Bondi]

Hi Paul,

the answer to your problem is easy.

When you decide to use a WIN2K server platform in your IT
infrastructure, you have to "think" in the new WIN2K
environment and, consequently, you have to abandon the old
WINNT mode.

When you decide to migrate your infrastructure to the
WIN2K platform, first of all you MUST decide what sort of
structure you will create.

In your case, suppose you have FOUR different sites.
In this case, the easier way is to create a structure with
SINGLE DOMAIN and MULTIPLE SITES.
To built this structure you'll need at least FOUR domain
controller, one for each site.

FIRST STEP
==========
THE FIRST STEP to do is to introduce the NEW PDC using the
WIN2K server in MIXED MODE.
Once you have done this, your actual PDC will become a BDC
recognized by the WIN2K primary.
Since the NEW PDC is now the NEW WIN2K server, he will
install the DDNS (Dynamic DNS) and this server will become
the new DNS for this site.
You'll have also to install the DHCP and the WINS durig
the installation process (but, of corse, you can always do
this in a second moment).
Note that when you install these services in the new WIN2K
server, you will have to stop the original services
running in the NT 4 machine.
At the end of this operation, your domain will have ACTIVE
DIRECTORY installed and the FIRST SITE active, with all
the service active.
Note that this first server is a GLOBAL CATALOG server;
this is very important.

SECOND STEP
===========
THE SECOND STEP to do is to create (with the ACTIVE
DIRECTORY SITES AND SERVICES) the other sites and the
other subnets.

THIRD STEP
==========
Then, THE THIRD STEP is to add an ADDITIONAL DOMAIN
CONTROLLER for the second SITE in the organization.
To do this, the easiest way is to add and additional WIN2K
DC to the FIRST site and the to MOVE this server in the
second SITE of the organization.
Install in the second DC all the DNS, DHCP and WINS
services but DO NOT CONFIGURE IT.

============
ATTENTION!!!
============

Once you have added the SECOND domain controller to the
FIRST SITE of the organization, BE SURE THE SECOND SERVER
IS A GLOBAL CATALOG SERVER!!!!
This is vital because when you move the server to the
SECOND SITE, this server will be able to AUTHENTICATE
LOCALLY all the users without the necessity to contact the
server lcated in the first site.
AT THIS POINT, the Active Directory Site and Services will
generate a new AD CONNECTION named "<automatically
generated>".
At this point the DNS server will be automatically
configurated by the ACTIVE DIRECTORY and it will start to
exchage information dynamically with the first DNS.
Now, you can proceed and install the DHCP server FOR THE
LOCAL SUBNET OF THE SITE and, finally the WINS server.
Once you have installed the DHCP server in the SECOND site
(second machine) the new DHCP entries will be
automatically notified to the local DNS and, when it will
occur the next Active Directory replication, the new
record will be replicated to the FIRST DNS and viceversa.

Of course, for the DHCP "Scope Options" in each site, you
will have to indicate the appropriate addresses for the
LOCAL DNS, DHCP and WINS server.

Finally, remember to include the replication partner for
the WINS server in each site and the new Active Directory
domain is completed!!!!

Repeat the steps for each site in the organization and if
all the operation are done correctly the new domain will
work.

The conclusion is:

1) with the Active Directory correctly configured ALL DNS
will update AUTOMATICALLY; you will not have to do NOTHING;

2) each site use the LOCAL DHCP scope; all the variations
are notified to the LOCAL DNS and, in a second time, the
LOCAL DNS will replicate the information with the OTHER
DNS. Of course, the other DNS will do the same;

3) each site use the LOCAL WINS server; with the
replication partner, all the data will be replicated
TO/FROM the other sites; you only have to indicate the
replication interval;

4) with an appropriate settings of the replication, the
WAN traffic is reduced


Well, I hope my indications will help you!

Have a nice day and don't hesitate to migrate to WIN2K;
it's very powerful!!

Tell me you comments.

Bye!!

MORENO
(Italy)