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.