| Author |
Message |
Kate
Guest
|
 Posted:
Fri Jan 28, 2005 10:55 pm Post subject:
New 2003 Domain w/ old DNS |
|
|
My company has an NT domain but we are currently creating a new domain with
server 2003 (keeping the old domain too). This new domain will be used for a
specific system we are implementing.
My question is can I use the DNS that is currently in our old domain for the
new one or will this cause conflicts? The DNS is supplied by our ISP and the
new domain needs to be on the internet.
Thank you.
Kate |
|
| Back to top |
|
 |
Danny Sanders
Guest
|
| Posted:
Fri Jan 28, 2005 11:05 pm Post subject:
Re: New 2003 Domain w/ old DNS |
|
|
No.
AD must have a DNS server set up for the AD domain. The DNS server must
support SRV records. Do not use your ISP's DNS server.
Set up DNS on the Win 2k3 server, point the DNS server to itself for DNS in
the properties of TCP/IP. Point all AD clients to the DNS server you set up
for the AD domain ONLY. For Internet access *usually* you would set up
forwarders and list your ISP's DNS server as the forwarder, but in your case
you may want to forward to your NT DNS server.
See:
Best Practices for DNS Client settings in Windows 2000 server and in Windows
Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;825036
Setting Up the Domain Name System for Active Directory
http://support.microsoft.com/default.aspx?scid=kb;en-us;237675
How to configure DNS for Internet access in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;323380
hth
DDS W 2k MVP MCSE
"Kate" <Kate@discussions.microsoft.com> wrote in message
news:415BC083-1A95-469B-8F89-482BDD1F56F6@microsoft.com...
| Quote: | My company has an NT domain but we are currently creating a new domain
with
server 2003 (keeping the old domain too). This new domain will be used
for a
specific system we are implementing.
My question is can I use the DNS that is currently in our old domain for
the
new one or will this cause conflicts? The DNS is supplied by our ISP and
the
new domain needs to be on the internet.
Thank you.
Kate |
|
|
| Back to top |
|
|
Kevin D. Goodknecht Sr. [
Guest
|
| Posted:
Fri Jan 28, 2005 11:15 pm Post subject:
Re: New 2003 Domain w/ old DNS |
|
|
In news:415BC083-1A95-469B-8F89-482BDD1F56F6@microsoft.com,
Kate <Kate@discussions.microsoft.com> commented
Then Kevin replied below:
| Quote: | My company has an NT domain but we are currently creating
a new domain with server 2003 (keeping the old domain
too). This new domain will be used for a specific system
we are implementing.
My question is can I use the DNS that is currently in our
old domain for the new one or will this cause conflicts?
The DNS is supplied by our ISP and the new domain needs
to be on the internet.
|
You should use the Win2k3 DNS, it supports Dynamic DNS updates (secure and
non-secure), SRV records, and some other options NT4 does not support.
What you can do is use the NT4 DNS as a conditional forwarder on Win2k3 for
the zones it holds.
But all members of the AD domain must use the DNS that supports the AD
domain.
--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
=================================== |
|
| Back to top |
|
|
Herb Martin
Guest
|
| Posted:
Sat Jan 29, 2005 4:15 am Post subject:
Re: New 2003 Domain w/ old DNS |
|
|
"Kate" <Kate@discussions.microsoft.com> wrote in message
news:415BC083-1A95-469B-8F89-482BDD1F56F6@microsoft.com...
| Quote: | My company has an NT domain but we are currently creating a new domain
with
server 2003 (keeping the old domain too). This new domain will be used
for a
specific system we are implementing.
My question is can I use the DNS that is currently in our old domain for
the
new one or will this cause conflicts? The DNS is supplied by our ISP and
the
new domain needs to be on the internet.
|
Not as the Primary, unless it supports Dynamic DNS
(which NT does not.)
You can use an (updated) NT4 DNS server as a secondary.
You do NOT want to mix the JOBS of the EXTERNAL
and the INTERNAL DNS servers so that part is GOOD.
DNS for AD Domains:
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domain (either directly or indirectly)
Restart NetLogon on any DC if you change any of the above that
affects a DC and/or use:
nltest /dsregdns /server:DC-ServerNameGoesHere
Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.
Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.
Single Lable domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
--
Herb Martin
|
|
| Back to top |
|
|
troy240sx@yahoo.com
Guest
|
| Posted:
Sat Jan 29, 2005 5:03 am Post subject:
RE: New 2003 Domain w/ old DNS |
|
|
We are kind of doing the same thing, not the whole external ISP/DNS thing but
we are doing a migration from one domain to another. NT to 2003 AD with
different domain names. I found it best for us to do the following:
Setup AD and integrated secure dynamic DNS (keeping your other DNS intact)
Setup stub zones in the AD DNS for your old DNS zones. We did this because
you can't have integrated secondary zones.
We setup scavenging to keep the dynamic records clean.
Then change your DHCP scopes to hand out the new DNS servers to all your
clients. They will be able to resolve all records in either the AD or old
DNS zones, granted that they are using FQDNs. If they are not using FQDNs
you will have to add a suffix list to their DNS settings. Unfortunately you
cannot have a suffix list pushed out via DHCP. There is a GPO that allows
you to change it only for XP (that I have yet to see work). Creating a
script to remotely add suffix list to a list of computers is easy to create
though. We are just migrating DNS records to the new AD zone as we migrate
projects that need them.
You could also create a normal primary zone on the AD DC(non-intergrated)
and copy and paste all the records from your zone file in the old zone to the
new zone (don't forget to restart the DNS Server service afterwards). Then
integrate the zone into AD afterwards.
The only reason we chose the first option was because we have a lot of crap
records that people enter and don't delete when their done. It will give us
a chance to clean house... :)
Hope this helps...or at least gets you in the right direction...
"Kate" wrote:
| Quote: | My company has an NT domain but we are currently creating a new domain with
server 2003 (keeping the old domain too). This new domain will be used for a
specific system we are implementing.
My question is can I use the DNS that is currently in our old domain for the
new one or will this cause conflicts? The DNS is supplied by our ISP and the
new domain needs to be on the internet.
Thank you.
Kate |
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in