It222 Week 1
Research assignment Part 2 1. Purpose of the Global Names Zonein Windows Server 2008 DNS Servers
GNZ is intended to aid the retirement of WINS, and it's worth noting that it is not a replacement for WINS. GNZ is not intended to support the single-label name resolution of records that are dynamically registered in WINS, records which typically are not managed by IT administrators. Support for these dynamically registered records is not scalable, especially for larger customers with multiple domains and/or forests. In GNZ, after the creation and enabling of the GlobalNames zone, the administrators must manually create, add, edit and, if required - delete, name records from that zone. GNZ does not support dynamic updates 2. Modifications Necessary to DNS for accomodating Read Only Domain Controllers. How is it different from the way DNS handles ordinary Domain Controllers?
Make sure to configure RODC to point to itself as the preferred DNS server. In addition to the zone corresponding to the AD domain that RODC is part of, DNS should be hosting DomainDNSZones and ForestDNSZones application partitions (which you can configure using dnscmd command line utility).
An ordinary Domain Controller can do nifty things, like add a new user/group, make mods to it's own system to accommodate updates, ect. A Read Only Domain Controller can only be changed by a main Domain Controller making updates to it. 3. Explain Background Zone Loading
Background zone loading is a feature of Windows Server 2008. In this feature, a DNS server on Windows Server 2008 loads zone data from AD DS in the background while the server restarts so that it can respond to the queries from other zones. Because the zone loading is performed by separate threads, the DNS server can reply queries during the zone loading process. This feature is helpful when restarting a DNS server takes a long time due to loading of large zone data and the DNS server is effectively unavailable to service client
GNZ is intended to aid the retirement of WINS, and it's worth noting that it is not a replacement for WINS. GNZ is not intended to support the single-label name resolution of records that are dynamically registered in WINS, records which typically are not managed by IT administrators. Support for these dynamically registered records is not scalable, especially for larger customers with multiple domains and/or forests. In GNZ, after the creation and enabling of the GlobalNames zone, the administrators must manually create, add, edit and, if required - delete, name records from that zone. GNZ does not support dynamic updates 2. Modifications Necessary to DNS for accomodating Read Only Domain Controllers. How is it different from the way DNS handles ordinary Domain Controllers?
Make sure to configure RODC to point to itself as the preferred DNS server. In addition to the zone corresponding to the AD domain that RODC is part of, DNS should be hosting DomainDNSZones and ForestDNSZones application partitions (which you can configure using dnscmd command line utility).
An ordinary Domain Controller can do nifty things, like add a new user/group, make mods to it's own system to accommodate updates, ect. A Read Only Domain Controller can only be changed by a main Domain Controller making updates to it. 3. Explain Background Zone Loading
Background zone loading is a feature of Windows Server 2008. In this feature, a DNS server on Windows Server 2008 loads zone data from AD DS in the background while the server restarts so that it can respond to the queries from other zones. Because the zone loading is performed by separate threads, the DNS server can reply queries during the zone loading process. This feature is helpful when restarting a DNS server takes a long time due to loading of large zone data and the DNS server is effectively unavailable to service client