RE: DNS question, NT inplace upgrade to 2003 AD

Hello,

Thank you for your reply!

More suggestions for your reference:

1. You may make a BDC and move the DNS file from the old PDC DNS server to
the new BDC. Then promote the BDC to PDC and perform an in-place upgrade to
Windows 2003 on the BDC.

More information for your referernce:

172221 How to move one or more zone files to a new Windows NT DNS server
<http://support.microsoft.com/default.aspx?scid=kb;EN-US;172221>

Upgrading a Windows NT 4.0 domain to Windows Server 2003
<http://www.networkclue.com/os/Windows/server/nt-2003-migration.aspx>

This response contains references to third party World Wide Web sites.
Microsoft is providing this information as a convenience to you. Microsoft
does not control these sites and has not tested any software or information
found on these sites; therefore, Microsoft cannot make any representations
regarding the quality, safety, or suitability of any software or
information found there. There are inherent dangers in the use of any
software found on the Internet, and Microsoft cautions you to make sure
that you completely understand the risk before retrieving any software from
the Internet.


Hope the information helps.

Best Regards,

Jason Tan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.




--------------------
| Thread-Topic: DNS question, NT inplace upgrade to 2003 AD
| thread-index: AcYd654+Jh2BJBlTSO+1/91AGqkOXA==
| X-WBNR-Posting-Host: 208.252.89.2
| From: "=?Utf-8?B?bWlrZXMxcA==?=" <mikes1p@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <8FB31504-AC99-4CF9-9A2E-459C2F34BD05@xxxxxxxxxxxxx>
<uDBDZuaHGHA.3944@xxxxxxxxxxxxxxxxxxxxx>
| Subject: RE: DNS question, NT inplace upgrade to 2003 AD
| Date: Fri, 20 Jan 2006 10:02:03 -0800
| Lines: 138
| Message-ID: <192B4EA5-994F-4100-95D4-59C544D1D866@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.windows.server.migration
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.windows.server.migration:22118
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| Thanks for the reply
|
| How do I upgrade or move our primary DNS server to Server 2003? Our
current
| primary DNS server is our NT4 PDC and is too old to upgrade to 2003. I've
| searched MS and read many doc's but haven't found the answer to this
|
| Can someone point me in the right direction?
|
| Thanks
| Mike
| "Jason Tan (MSFT)" wrote:
|
| > Hello,
| >
| > Thanks for posting!
| >
| > I suggest you install a Windows Server 2003 on the new hardware and
attempt
| > to configure a secondary name Server in Windows Server 2003.
| >
| > Configure the Forward Lookup Zone
| >
| > To configure the forward lookup zone on the secondary name server,
follow
| > these steps:
| >
| > 1. Log on to the secondary name server as an administrator.
| > 2. Click Start, point to Administrative Tools, and then click DNS.
| > 3. In the console tree, under DNS, click Host name (where Host name is
the
| > host name of the DNS server).
| > 4. In the console tree, click Forward Lookup Zones.
| > 5. Right-click Forward Lookup Zones, and then click New Zone.
| > 6. When the New Zone Wizard starts, click Next to continue.
| > 7. Click Secondary Zone, and then click Next.
| > 8. In the Name box, type the name of the zone (for example,
example.com),
| > and then click Next.
| > 9. On the Master DNS Servers page, type the IP address of the primary
name
| > server (Windows NT server) for this zone, click Add, click Next, and
then
| > click Finish.
| >
| > For more detailed information please refer to the following article:
| >
| > 816518 HOW TO: Configure a Secondary Name Server in Windows Server 2003
| > http://support.microsoft.com/default.aspx?scid=kb;EN-US;816518
| >
| > More information for your reference:
| >
| > Migrating Windows NT Server 4.0 Domains to Windows Server 2003 Active
| > Directory
| >
<download.microsoft.com/download/2/9/6/2964bd25-6221-45a3-8115-a547cd640cd4/
| > NT4domtoad.doc>
| >
| > Hope the information helps.
| >
| > Best Regards,
| >
| > Jason Tan
| >
| > Microsoft Online Partner Support
| > Get Secure! - www.microsoft.com/security
| >
| > =====================================================
| >
| > When responding to posts, please "Reply to Group" via your newsreader
so
| > that others may learn and benefit from your issue.
| >
| > =====================================================
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| >
| >
| >
| >
| >
| >
| >
| >
| > --------------------
| > | Thread-Topic: DNS question, NT inplace upgrade to 2003 AD
| > | thread-index: AcYdIMbggSw+1FXKRq++rU8O8tP7Yw==
| > | X-WBNR-Posting-Host: 208.252.89.2
| > | From: "=?Utf-8?B?bWlrZXMxcA==?=" <mikes1p@xxxxxxxxxxxxxxxxxxxxxxxxx>
| > | Subject: DNS question, NT inplace upgrade to 2003 AD
| > | Date: Thu, 19 Jan 2006 09:50:03 -0800
| > | Lines: 26
| > | Message-ID: <8FB31504-AC99-4CF9-9A2E-459C2F34BD05@xxxxxxxxxxxxx>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | charset="Utf-8"
| > | Content-Transfer-Encoding: 7bit
| > | X-Newsreader: Microsoft CDO for Windows 2000
| > | Content-Class: urn:content-classes:message
| > | Importance: normal
| > | Priority: normal
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| > | Newsgroups: microsoft.public.windows.server.migration
| > | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| > | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
| > | Xref: TK2MSFTNGXA02.phx.gbl
| > microsoft.public.windows.server.migration:22102
| > | X-Tomcat-NG: microsoft.public.windows.server.migration
| > |
| > | I am trying to determine how to keep our DNS working while I upgrade
our
| > NT
| > | domain to 2003 AD. I do have a lab that is close to our production
domain
| > but
| > | I can't recreate all the clients. We have an NT4 PDC running DNS and
an
| > NT4
| > | BDC running DNS as a secondary/read only. I have new hardware that I
will
| > | install as an NT4 BDC, promote to PDC, then upgrade to 2003 and AD in
| > mixed
| > | mode.
| > |
| > | We have 400+ devices and client PC's that use our two DNS servers
(.16
| > and
| > | .17) and it's not practical for me to change the DNS settings on
every
| > | device. Ultimately I want to have 2003 DC's running DNS with the .16
and
| > .17
| > | IP addresses.
| > |
| > | My plan is to keep the original PDC (.16, demoted to a BDC) on the
LAN
| > until
| > | I have two AD DC's since it the primary DNS server for everything.
| > |
| > | What is the best way to get our DNS records onto the first AD DC?
Should
| > I
| > | install DNS on the new temp NT BDC/PDC hardware so the DNS records
are in
| > | place for the upgrade, then upgrade to 2003 and AD? Or is there a
better
| > way?
| > |
| > | Our current PDC/DNS at .16 cannot run 2003, my plan is once there is
a
| > | second DC with DNS running I will change one of the DC's to the .16
IP
| > | address. Any problems doing this?
| > |
| > | Just don't want to dig myself into a hole
| > | Mike
| > |
| > |
| >
| >
|

.

Relevant Pages

  • Re: BDC DCDIAG Problem
    ... DNS" in the TCPIP properties and setting the adapters' DNS server order such ... PDC and BDC are obsolete terms, ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.sbs)
  • Re: BDC DCDIAG Problem
    ... What I found was my backup was not set to register in DNS and I set each DC ... PDC and BDC are obsolete terms, ... server Security Configuration Wizard on this server perhaps? ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.sbs)
  • Re: BDC DCDIAG Problem
    ... server Security Configuration Wizard on this server perhaps? ... the DNS was removed and reinstalled on the BDC, ... Have run DCDIAG on BDC and still have error - This is where I need ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.sbs)
  • Re: BDC DCDIAG Problem
    ... server Security Configuration Wizard on this server perhaps? ... the DNS was removed and reinstalled on the BDC, ... Have run DCDIAG on BDC and still have error - This is where I need ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.sbs)
  • Re: BDC DCDIAG Problem
    ... I am looking through my DNS entries and I am only able to find SRV records ... for the PDC and not the BDC. ... Are there supposed to be records for the BDC as ... server Security Configuration Wizard on this server perhaps? ...
    (microsoft.public.windows.server.sbs)
Loading