Solved

NT4 to Win2003 Upgrade DNS question  Related to Q_22091364

Posted on 2007-03-30
1
213 Views
Last Modified: 2013-12-28
One more issue according to microsoft   and this has some logic.

Client domain name is Blonkovich currently  (Fake name for example).

The new domain in AD was going to be  Blonkovich.com  BUT the client has the LIVE WEBSERVER local.  They host the registered DNS outside.  Currently they use host files on each machine to point to the internal server for web and mail.  That works but is surely very ugly.

I added the local address to DNS for mail and www.  It works fine.  BUT the Microsoft techs mentioned that a host could get the info from the outside DNS and then not be able to resolve.

I am really unsure how this could occur since the only DNS they would use would be the internal and they would both have the local address.

Anyway they recommended we name is Blonkovich.local.  Any reason I should or should not do this?

Also any special circumstances surrounding HOW I NAME the forest/domain.  IE is it best to namke it the same as the NT Current domain just adding .com or .local or is it irrelavant?

Lastly they may want to someday add this domain to another forest.  How does the current name impact this.

Too many questions I know.
0
Comment
Question by:dcohn
1 Comment
 
LVL 83

Accepted Solution

by:
oBdA earned 500 total points
ID: 18828516
If in doubt, go for whatever.local. This is the company's *AD* *domain*. It's for management of their LAN, it has nothing to do with its internet presence. Microsoft chose DNS as name resolution for AD, but that doesn't mean the AD domain's DNS name has to be the same as the external presence. Note that this will *not* keep them from using john.doe@company.com as email address, even if using Exchange.
Some pros and cons for either solution are listed here (already posted in the other question, and still valid for most installations, not only SBS):
The Domain Name System name recommendations for Small Business Server 2000 and Windows Small Business Server 2003
http://support.microsoft.com/?kbid=296250

It doesn't really matter how you name it. You will have two domain names, the backward compatible NetBIOS domain name it currently has, and the new AD DNS name. They can have BLONKOVICH as NetBIOS domain name and microsoft.local as AD DNS name, and apart from some possible confusion for the users, the domain itself couldn't care less.
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Our Group Policy work started with Small Business Server in 2000. Microsoft gave us an excellent OU and GPO model in subsequent SBS editions that utilized WMI filters, OU linking, and VBS scripts. These are some of experiences plus our spending a lo…
In this article, I will show you HOW TO: Perform a Physical to Virtual (P2V) Conversion the easy way from a computer backup (image).
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7. Start the SARDU utility: Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

920 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now