Link to home
Start Free TrialLog in
Avatar of YaYangTeah
YaYangTeahFlag for Malaysia

asked on

DNS Server

In company we have two DNS server is to serve for the other company domain name.
NS1.abc.com --Okay
NS2.abc.com--Down
Currently our second NS2 is down due to hardware faulty so my boss give me one server to set-up the NS2. Please advice what is faster and easy way the set-up this NS2. Shall I export all the DNS entry from NS1 and import to NS2? If yes, please let me know the
Avatar of Gregory Miller
Gregory Miller
Flag of United States of America image

Just build it and it will begin caching the requests on its own. You do not need to copy anything. If you are talking about duplicating your zones from NS1 then set the two servers to sync themselves to each other. This will allow any change made to NS1 to automatically be copied to NS2 and vice-verse.

How - depends a lot on what DNS service you use and what OS this is.
ASKER CERTIFIED SOLUTION
Avatar of Mahesh
Mahesh
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
AXFR and IXFR is the best way to design MS DNS.

TY/SA
Agree with Technodweeb.  Set up the second server, I'd set up as NS3, not 2 which 'did' exist.  Set up to sync and the records will populate.

- gurutc
Avatar of YaYangTeah

ASKER

I already setup the new DNS server yesterday,
I was manually tranfer the zone to the ns2 as the secondary DNS. Eventually I try to promote the new ns2 as the secondary domain controller but I facing the issue to do adprep /forest  in primary domain controller which is NS1, I guess this is because server keep replicate to old NS2, so I may need do some clean out for the Old NS2 then can do the adprep again. Please advice how to do the clean out for the offline domain controller  ?
You don't need to run ADPREP, just run dcpromo in order to promote it to ADC, but 1st cleanup metadata for failed DC

Metadata cleanup:
Follow step by step process mentioned in below TechNet article to cleanup failed DC metadata
http://technet.microsoft.com/en-us/library/cc816907(v=ws.10).aspx

http://www.petri.co.il/delete_failed_dcs_from_ad.htm

Mahesh
Running ADprep or not depends upon the OS level of the new DC you are trying to introduce in network

If its higher version for e,g your existing DC is 2008 and new DC is 2008 R2 then you may need to run adprep

You may also compare the schema version for which refer below link
http://kpytko.wordpress.com/2011/10/06/schema-version/

Run netdom query fsmo and make sure that the dead DC does not own any FSMO roles
if there are FSMO roles on dead DC then follow below link and perform seizure of Roles

Seize FSMO role:
http://www.petri.co.il/seizing_fsmo_roles.htm
The primary domain controller is w2k3 and the server i desire to promote is w2k8 r2 currently all the roles still in primary controller
So your current schema version must be 30 ..Please confirm using below command (Edit the domain and local as per your domain naming convention)

dsquery * “cn=schema,cn=configuration,dc=domain,dc=local” -scope base -attr objectVersion

Open in new window




In this case you need to update schema
Refer below link for how to upgrade schema

http://kpytko.pl/2011/08/25/adding-first-windows-server-2008-r2-domain-controller-within-windows-2003-network/