DNS replication when installing new DC in domain

New year 2006 greetings,

I'm preparing for win2003 upgrades for some small businesses, and
am developing a technical project plan in my lab.
These LANs all have an  NT4 Sp6 production server
with simple netbios domain names.

I am planning on a *temp* NT4 server to promote offline to PDC in
a private network, then upgrade to Win2k3 SP1 on that temp  machine.

Then, on the production (actual replacement) server do a clean install
of 2003 on raid 5, grab 5 fsmo roles, make it a GC, set up DNS then demote the original server. This way, the 2003 production box will have same IP address, same domain sid, and same name as the original NT 4 server.

------------------------------------------------
I have two general DNS questions regarding this procedure

1.  During the install of 2003 on my temp PC, I need to choose
an appropriate domain name for the AD forest.  Because they
are non-profits, I don't want to use .com, and I hesitate to use
..org as these clients don't have a web presence, or even a plan for one
  Assuming the existing NT4 domain is named  HEALTHCARE,
I have used healthcare.local in my lab, and all seems to go fine.
Reason for .local as a suffix is to differentiate it from a future
web site hosted outside the firewall using .org or .info
Is there a recommended Naming format for AD forests, where the business
does not anticipate ever having an internally hosted web server that
is resolvable from the outside? Any issues with using .local when
Longhorn server/client is released?


2 When setting up DNS on the production 2003 server (2nd DNS server in this domain) what's the correct way to make it a DNS server, and
have all the zones transfer, including RDNS?

Two methods I've tried
A> Just install DNS on the 2nd server in the domain, and replication will take care of the zone tranfer.

or

B> Quoting from the help files for 2003 server, it says
"On the Action menu, click New Zone.
Follow the instructions in the New Zone Wizard.
When adding the zone, select Secondary zone as the zone type"

Method A just doesn't seem to work, even though DCdiag says no
replication problems, even after waiting hours.

Method B  does transfer the zones, but I have doubts about the process,
as the *temp* server will be removed when doing this in production.
When I demote the *temp* server, and remove that from the domain using
ADUC, is DNS going to function ok on the production server?

Thanks for your responses.

LK





.

Relevant Pages

  • RE: exchange server cannot mount mailbox store
    ... What's the exact detailed DNS Events ... Type desired internal IP address of your SBS server. ... it will delete the reverse lookup zone if the zone no longer ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Event 4515 :another copy of zone has been found
    ... running on the old 2000 server. ... I then installed DNS on ... I seem to remember hearing that if you just delete/remove the zone it ... Container), the Configuration Partition, and the Schema Partition. ...
    (microsoft.public.windows.server.dns)
  • Re: Replication between parent child domains
    ... install dns before i run the dcpromo on the melbourne server. ... DNS server will forward any query it can't answer, Checks zone ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replication between parent child domains
    ... DNS server will forward any query it can't answer, Checks zone ... DNS Servers) all queries will go to tld DNS server (including Internet ... Stub zones: Stub zones contain a read-only copy with specific records ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS Redesign Issue
    ... -Using DNS console you can right-click the zone and export to a File, ... -To export a Zone and import that Zone in another DNS Server you need to use ... Create a child zone dallas on the DNS server in the child domain ...
    (microsoft.public.windows.server.dns)