• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 694
  • Last Modified:

Exchange 2010 and internal/external DNS

I'm sure this is an easy one, but I can't seem to wrap my head around it.  

#1 I have an SBS 2003 server with a FQDN of srvr1.easyco.local.  I have just added a new windows 2008 R2 server to the
network wi th a new forest  and it's FQDN is srvr1.easyco98.local. (Eventually we are phasing out the sbs 2003 that's why
I've started a new forest - but that's another topic.) On the new 2008 R2 server I'm only going to run Exchange 2010.  
My workstations all look to the SBS 2003 server for their default DNS.  I'm stumped on what I need to add on the sbs 2003
DNS so that all my workstations can resolve the new server name.  I've tried a few things and with some success, but I need
the experts to advise me on this.  

#2 Since I'm using a .local as my domain name what happens when I'm outside the network with my laptop and open Outlook?  Is it going
to be looking for the .local name?

This is my first experience with exchange, I've been a GroupWise admin for many years and struggling.

Thanks in advance for any help you can give this old dog.  Please teach me new tricks.  
0
tparrett
Asked:
tparrett
  • 3
  • 2
1 Solution
 
Glen KnightCommented:
I wouldn't recommend a new forest, there is no need and it will cause mire problems than it will solve since SBS doesn't support trusts.

My recommendation would be to follow my migration guide here: http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2881-Migrate-Small-Business-Server-2003-to-Exchange-2010-and-Windows-2008-R2.html
0
 
tparrettAuthor Commented:
wow - demazter - this is a great document.  I plan on gong through it step by step later today.  I have one other question though.  The SBS server (I inherited it) was totally configured for Exchange, but they had never used it.  Do you think I should still go through the full migration?

Thanks
0
 
Glen KnightCommented:
Yes, I would still recommend doing the whole procedure.
0
 
tparrettAuthor Commented:
I'm justing going through the doc and notice that the last step #13 DCpromo SBS 2003 server so it is no longer a domain controller and remove from network.  In my scenario we are still using the SBS 2003 server.  We're just adding a 2008 R2 and installing exchange.  Can I just stop after the 12th step?

Thanks again for all your help.  It is greatly appreciated.
0
 
Glen KnightCommented:
Yes, if you are not removing SBS then don't transfer the FSMO roles or DCPROMO the SBS server.
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now