Re: DNS...Where Should Secondary Point To?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

In news:47c021e9-0d94-4fd4-aabf-5c7da0e88cad@xxxxxxxxxxxxxxxxxxxxxxxxxxxx,
nc <cipher7836@xxxxxxxxx> typed:

This is great information! Thanks so much!

No problem. I saw some of the links didn't show up right. I'm reposting it
below so it will be easier to click on.

Ace
==============
If you havea a third new DC, promote it to be a DC in the same domain. Then
install DNS. Assuming the current zone is AD integrated, DO NOTHING ELSE.
Sit there and wait. Go to lunch. Upon return, you will find the zone has
automatically populated. Because AD integrated zones are in the actual AD
database, it will automatically replicate to the new machine by the default
AD replicationprocess. There is really nothing else to configure on this
part, that is assuming the zone is already AD integrated. Is it AD
integrated? If so, what scope is it set to on both machines?

Change the ip properties of this DC to use one of the other DCs as the first
entry, the second as itself. That;s it for this part. I fnot sure how,
follow this article:
825036 - Best practices for DNS client settings in Windows 2000 Server and
in Windows Server 2003
http://support.microsoft.com/?id=825036

Go into DNS properties, configure a Forwarder to your ISP's DNS. If not sure
how, this article will show you:
323380 - HOW TO Configure DNS for Internet Access in Windows Server 2003
(forwarding) :
http://support.microsoft.com/?id=323380

Install WINS. In IP properties, Advanced, WINS tab, ONLY point the WINS
address of itself to itself ONLY. Do not add any other WINS addresses. If
not sure how, follow this article:
WINS Best Practices (Use ONLY itself in ip properties):
http://technet2.microsoft.com/windowsserver/en/library/ed9beba0-f998-47d2-8137-a2fc52886ed71033.mspx

Once that is done, change the WINS address to the new server in DHCP Option
046. Make sure you have DHCP Option 044 set to 0x8.

If you say the other DCs are that unreliable, transfer all the FSMO roles to
this new server.If not sure how, follow this article:
How to view and transfer FSMO roles in Windows Server 2003:
http://support.microsoft.com/kb/324801

Make this DC a GC. If not sure how, follow this article:
http://technet2.microsoft.com/windowsserver/en/library/93ffc6d8-e4c9-4a5b-8b4c-7d426bcba5a11033.mspx?mfr=true





.

Relevant Pages

  • RE: NT->AD2003 upgrade
    ... server to Windows Server 2003. ... If the existing DNS zones are AD-integrated, ... Method 1: Zone Transfer ... Create a secondary zone on the Windows Server 2003 system for the zone ...
    (microsoft.public.windows.server.migration)
  • Re: New DC 2003
    ... prior to the schema update, or upgrade it to Exchange 2003. ... Upgrading Windows 2000 Domains to Windows Server 2003 Domains: ... How to move Windows 2000 DNS zones to another Windows 2000-based server: ... choosing import from file as the source during the zone creation wizard. ...
    (microsoft.public.windows.server.networking)
  • RE: W2K to new W2K3 server: Best way to move DNS and DHCP ?
    ... Do you have an AD-integrated zone in the target win2k3 domain now? ... We have several methods to seamlessly migrate DNS zones from a Windows 2000 ... server to Windows Server 2003. ... Create a secondary zone on the Windows Server 2003 system for the zone ...
    (microsoft.public.windows.server.migration)
  • Re: DNS Server Event 4515
    ... THis all started after a DC running DNS Failed and it ... The zone pfeinc.com was previously loaded from the directory partition ... Are all Domain Controllers in the domain running Windows Server 2003? ...
    (microsoft.public.windows.server.dns)
  • Re: Single NT 4.0 domain upgrade
    ... DNS is configured to respond on the internal interface ... Since you will have 2 DCs it is advisable to run DNS ... FSMO roles and whether you have a GC. ... > I think there was already a zone defined from when I have ...
    (microsoft.public.windows.server.dns)