setup backup DNS server

Hi,
  I have SBS2011 Server running DNS server and like to create a backup DNS server on a separate 2008 server box.
  Can someone give me step by step instructions?

Thanks.
LVL 1
sgleeAsked:
Who is Participating?
 
footechCommented:
In that case, please read this link:
http://www.petenetlive.com/KB/Article/0000379.htm

I have little experience with VMware, but it looks like AD LS is required by vCenter, so it can not be installed on a domain controller.

So it looks like you either need to:
1) setup another machine as a DC
2) put vCenter on some other machine
3) abandon the thought of a second DC and just set up DNS
My personal preference would be to go with option 1 or 2, because of the advantages you get with having a second DC, but the choice is yours.
0
 
meko72Commented:
on the existing server, under 'namesrevers' tab, add the new name server.
on the existing server, under 'zone transfer' ensure that transers are permitted to only the servers on the name servers tab

on the new server, create a new secondary zone.
add the ip address of the current master server.

it should automatically replicate.

Also here is a technet Article  http://technet.microsoft.com/en-us/library/cc816885(v=ws.10).aspx
0
 
footechCommented:
If all you want to do is have a backup DNS, the advice from meko72 is good.  But if the SBS is your only domain controller, then I would recommend setting up your additional server as a DC and DNS server.  This will give you much better redundancy than just a second DNS.

The process is simple.  Install the OS.  Add the Active Directory Domain Services role.  On the installation results page click the link to run DCPromo.  Choose the option to add a DC to an existing domain.  You will have the option to install DNS as an additional option (selected by by default).  Set a static IP for the machine if you haven't already done so.
Here's a link with more info.
http://technet.microsoft.com/en-us/library/cc753720%28v=ws.10%29.aspx

You won't need to make any change to your DNS settings.  It will all be AD-integrated so you won't have to mess around with zone transfers or anything.  The DNS zones will show up on your new server as soon as the data is replicated over, which should happen very quickly.

Afterwards, on the SBS you should open the DHCP console and edit the option for DNS servers and add the IP for the new server.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
shahzoorCommented:
Use any third party imaging software like Acronis
Simple to use and reliable
0
 
sgleeAuthor Commented:
Ldap 389 error
When I run Active Directory Domain Serviecs Installation Wizard, I get the above error.
0
 
meko72Commented:
you can allow and exception to that port on your firewall on the SBS also disble or allow that port aswell on the DC that your running DCpromo on.
if you have a good router/firewall, I would disable the firewalls on both the SBS and DC to elevate any replication issues.
0
 
footechCommented:
Is this a new machine that you're trying to install the AD DS role on or is there other software installed on it?  Is the new OS 2008 or 2008 R2?  Any other roles already installed?
You can use a command like "netstat -ano -p TCP" to see if the machine is using TCP 389 (you could exclude the -p switch if you want to check UDP as well).  If you find an entry with that port, match the PID to the process name using Task Manager or Process Explorer.  Or you could use TCPView for a GUI which should show you all on one screen.
You could try opening the port manually on the new machine, but the install process should take care of configuring the firewall automatically if you're using Windows Firewall.  Are you running another firewall?  I don't believe there is any need to modify anything on the SBS.
0
 
sgleeAuthor Commented:
This is NOT on SBS20011. I am trying to set up windows 2008 std (not R2) as backup domain controller. I have no firewall either on the router or this w2008 server.
0
 
sgleeAuthor Commented:
roles currently installedHere is screenshot of roles currently installed
0
 
sgleeAuthor Commented:
Here is the result of "netstat -ano -p TCP"  where port number 389 was found.
Where do I go from here?

  TCP    127.0.0.1:389          127.0.0.1:49193        ESTABLISHED     1328
  TCP    127.0.0.1:389          127.0.0.1:49346        ESTABLISHED     1328
  TCP    127.0.0.1:389          127.0.0.1:57626        ESTABLISHED     1328
  TCP    127.0.0.1:389          127.0.0.1:57627        ESTABLISHED     1328
  TCP    127.0.0.1:389          127.0.0.1:57749        ESTABLISHED     1328
  TCP    127.0.0.1:389          127.0.0.1:57750        ESTABLISHED     1328
  TCP    127.0.0.1:389          127.0.0.1:57876        ESTABLISHED     1328
  TCP    127.0.0.1:389          127.0.0.1:57877        ESTABLISHED     1328
  TCP    127.0.0.1:389          127.0.0.1:58163        ESTABLISHED     1328
  TCP    127.0.0.1:389          127.0.0.1:58164        ESTABLISHED     1328
  TCP    127.0.0.1:389          127.0.0.1:58271        ESTABLISHED     1328
  TCP    127.0.0.1:389          127.0.0.1:58272        ESTABLISHED     1328
  TCP    127.0.0.1:389          127.0.0.1:58402        ESTABLISHED     1328
  TCP    127.0.0.1:389          127.0.0.1:58403        ESTABLISHED     1328
  TCP    127.0.0.1:389          127.0.0.1:58512        ESTABLISHED     1328
  TCP    127.0.0.1:389          127.0.0.1:58513        ESTABLISHED     1328
  TCP    127.0.0.1:389          127.0.0.1:58778        ESTABLISHED     1328
  TCP    127.0.0.1:389          127.0.0.1:58779        ESTABLISHED     1328
0
 
footechCommented:
You match the PID (1328) to whatever is the process name as I mentioned in my previous post.  Basically what we're trying to do is determine what software is using port 389.  Once found you can decide whether it's something you need or not.

But I can almost definitely tell you that it is related to the having the AD LDS role installed.  You don't by any chance have VMware vCenter installed on this machine do you?
0
 
sgleeAuthor Commented:
"You don't by any chance have VMware vCenter installed on this machine do you?" --> I am glad you asked. Yes. I have VMWare ESXi V5 and Windows 2008 Std. Server is one of the Virtual Machines. I should have mentioned it in my original posting. Sorry about that.
0
 
sgleeAuthor Commented:
Let me repeat what you are saying.
I am experiencing this error because I am trying to set up this W2008 Server as domain controller within VMWare server?
0
 
footechCommented:
What I said was that you can't have vCenter installed on the same OS as a domain controller (apparently).  Going back through posts, I asked if you had this installed, and you said yes.  But maybe you only meant that you have a host running VMware, and on that host you have the guest VM running 2008.

So, to clarify, I'll ask, is the vCenter software installed on this guest VM?  If not, what other software is installed on it?
0
 
sgleeAuthor Commented:
VcenterOh... I understand your question now. Yes I have VCenter installed on this Windows 2008 STD that is at the same time a Virtual Machine.
0
 
footechCommented:
OK, so that's where the block comes from.  Not really from vCenter itself, but when you install it it adds the AD LDS role, and that's the one that using port 389 and blocking the install of AD DS.

So we're back to the 3 options that I mentioned before.
0
 
sgleeAuthor Commented:
OK. If the only reason I get this error is because VCenter, then I can un-install it from this W2008 and install it on another W2008 VM (with no VCenter). I don't have to run VCenter from this Windows 2008/Virtual Machine.
0
 
footechCommented:
OK.  Sounds good.  Not sure if the uninstall will automatically remove the AD LDS role, you may have to remove it manually.
0
 
sgleeAuthor Commented:
OK. I uninstalled every role ever installed on this W2008 Server. Restarted the server and it showed no roll installed. I am going to follow the suggestions below and post any questions.

"The process is simple.  Install the OS.  Add the Active Directory Domain Services role.  On the installation results page click the link to run DCPromo.  Choose the option to add a DC to an existing domain.  You will have the option to install DNS as an additional option (selected by by default).  Set a static IP for the machine if you haven't already done so.
Here's a link with more info.
http://technet.microsoft.com/en-us/library/cc753720%28v=ws.10%29.aspx

You won't need to make any change to your DNS settings.  It will all be AD-integrated so you won't have to mess around with zone transfers or anything.  The DNS zones will show up on your new server as soon as the data is replicated over, which should happen very quickly.

Afterwards, on the SBS you should open the DHCP console and edit the option for DNS servers and add the IP for the new server."
0
 
sgleeAuthor Commented:
OK. I completed creating new domain controller on this Win2008 Server. I attached post installation screen shots in WORD document and can you tell me if all looks good here?
DomainControllerServiceWizard.doc
0
 
footechCommented:
Didn't see anything that screamed at me.  You can use either 127.0.0.1 or the actual IP of the VM as the secondary DNS server.  Both will do the same thing.  Some people recommend to put itself as primary and another DNS server as secondary, but the latest recommendations from Microsoft are to do the reverse.  You may even see itself as the secondary, and 127.0.0.1 as the tertiary.

I assume you got past the first warning message that you posted.  DHCP looks good.

You should now be able to open the DNS console on either machine and see all the records.  Let me know if this is not the case.
0
 
sgleeAuthor Commented:
I checked DNS on both SBS2011 and new DC and they all look the same to me.
I also ran IPCONFIG /RENEW and it added an IP address of new DC:
--------------------------------------------------------------------------------------
      IP Address. . . . . . . . . . . . : 192.168.1.179
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Default Gateway . . . . . . . . . : 192.168.1.1
      DHCP Server . . . . . . . . . . . : 192.168.1.9
      DNS Servers . . . . . . . . . . . : 192.168.1.9
                                          192.168.1.3
--------------------------------------------------------------------------------------
Thanks for your help and let me close  the case now.
0
 
footechCommented:
Thanks.  It's also always a good idea (IMO) to run DCDIAG and DCDIAG /TEST:DNS on both machines after a setting up a new domain controller.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.