Design Group Policy for Your Infrastructure address the incorporation
When referencing naming conventions in Windows Server 2008, it’s essentially the same thing as saying you’re identifying the method of name to IP address conversion that is used throughout the enterprise. And of course, this brings to mind two different name resolution technologies that are used with Windows Server 2008: WINS and DNS.
Accordingly, this also means that the two MCITP Administrator technologies may either exist by themselves or coexist in the same environment. Furthermore, these technologies can be implemented either externally or internally. In the following sections, I’ll discuss some of the most com- mon usage scenarios for name resolution tactics and how they?re implemented in an enter- prise-level environment. I’ll begin with a brief review of DNS and zone types. Then, since I?ve already covered WINS technology, I’ll address the incorporation of WINS with DNS, and then I’ll address how to include Active Directory within DNS. Afterward, I’ll ?nish off this discussion on naming conventions by talking about some of the most commonly used migration, delegation, and transfer strategies used in a complex environment.
When I reference the words internal and external in regard to namespaces, I’m actually referring to whether you’re using the internal infrastructure of your enterprise, or how that Naming enterprise is accessed from the Internet. On the internal level, you usually reference your enterprise by an extension such as .local, whereas the external namespace is referenced by a top-level domain such as .net, .com, or .org. And each of these types of naming conven- tions, internal and external, make way for several Configuration options that are important in terms of administrative overhead and user accessibility.
In fact, the first design choice an administrator has to make when choosing an internal and external naming scheme is whether that naming scheme will actually be the very same scheme, that is, whether the internal and external naming address will MCITP Test be the same. It’s certainly a tempting option, and it has lulled more than a fair share of (perhaps lazy is too strong a word) less involved administrators.
When designing an internal namespace and an external namespace that use the same name, an administrator is choosing to have the internal namespace be a subdomain of the external namespace. The problems with this are, first, security based (because resources are all in one place) and, second, that users in the internal organization won?t be able to access external resources without a lot of overhead administrative work, which is basically taking away from one of the bene?ts of using them both at once.
When using different internal and external naming addresses, you’re provided with the added bene?t of security, and you create an additional forwarder in DNS. Plus, users who may be accessing your network externally will not have access to your internal resources, which is a huge bene?t.
Processing your request, Please wait....
