I'm having a problem with a split dns horizon. After migrating to AD from Novell my company decided to have a 3rd party build/host a web site for us. Since my local domain is .com I'm having trouble resolving the web site internally. I came across this expert advice and think it fits what I need. Can someone tell me how to go about changing my internal domain name from .com to .local?
>>DO NOT name the AD domain as the same as your DNS domain.
>>If you domain is QUANGO.COM then best practice is QUANGO.LOCAL
>>You then set the exchange server to route email for QUANGO.COM and as long as the MX records are in place for >>QUANGO.COM then everything will work fine.
>>The reason for this is to avoid SPLIT HORIZON DNS where you have to resolve machines on the same domain that are >>not on your local subnets. This is not insumountable, but is a pain in the ass that you don't have if the internal and >>external domain is different.
This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.