DNS situation



Current Environment
I Have 2 NT 4.0 Domains, "DomainA" & "Domain_C"

Most of the User and Computer accounts are in "DomainA",

"DomainA" has one PDC and one BDC.
Some other servers.

Some accounts and most of the Resources are in "Domain_C"

"Domain_C" has one PDC and one BDC
Mail server (OS: windows 2000 server)
Outlook Web Access (OS: windows 2000 server)
Primary and Secondary DNS, WINS, DHCP services(OS: windows
2000 server)
Print Server (OS: windows 2000 server)
SQL 2000 (OS: windows 2000 server)

Almost 99% of the clients in both Domains are on OS
Windows 2000 professional.

DNS servers have all static entries which
are like

which is being used by both the domains.

Server part in the above FQDN is local servers used by
local users and remote VPN clients.

ExternalDomainName.com is name owned by the company and
has a valid web presence.

New AD domain names (suggested) would be "DomainA" example
So full FQDN will be corp.externalDomainName.com

"Domain_C" will be child domain of Corp (suggested)
"Domain_C" example "DomC"
So full FQDN will be DomC.corp.externalDomainName.com

At the time of AD upgrade my Domain controller will look
for DNS servers
which are Authoritative for Domain "corp" and "DomC", If I
create DNS zones on DNS servers which will provide support
for resource records and Dynamic updates.All the systems
in these domains will try to create dynamic records, which
will ultimately create duplication with my existing

How will the DNS server's with static entries for the same
server names will handle these resolutions.

Since the static entries are saying

and the Dynamic entry will be

and how will it affect resolution on the client side.

(also consider the fact that I am keeping the WINS
services for a while after the upgrade)




Servers should always have static entries for their A records. The PDC
would be upgraded first so it will look for a dns authoritative for the zone
corp.externaldomainname.com if that is the active directory domain that will
be created. That makes the AD domain a subdomain of the DNS domain. You
will have to restructure your dns to allow for the
corp.externaldomainname.com subdomain. The server will register its service
records in that zone which must be a primary zone so the other zones will
have to be secondary and therefore get copies of the pdc's dns records.





Thanks Lee for your time for the reply.
I understand that new AD zones needs to be created on my
DNS server, which would be
In these zones all AD domain controllers will create
their respective SRV records.

My question is since DNS is the primary way to resolve
names to IP in Windows 200 Domain, what will happen when
client machines and other servers ( which are part of
these domains) will try to Dynamically register their
names .. Won't it create duplicate entries ?


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question