NT4 to Win2003 Upgrade DNS question Related to Q_22091364

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.
LVL 3
dcohnAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

oBdACommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.