Planning and Design Considerations
Once deployed, a DNS infrastructure can be difficult to change. Thorough planning is required to minimize the chance that you will need to make major changes to your DNS infrastructure. For example, if you name an intranet server server.contoso.com and later decide to move it to server.north.contoso.com, you would need to update every client application and bookmark that had the original server name stored before the change would take effect. Ultimately, you will save time by planning your DNS infrastructure around the future of your organization, including adding staff, expanding into regional offices, or merging with other organizations. This section describes planning and design considerations for a DNS infrastructure. ...
Get Windows Server® 2008 Networking and Network Access Protection (NAP) now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
