When a client is the precursor to an update request the DNS server on the RODC uses the domain controller locator to find domain controllers in the closest site. In the past, enterprises with zones containing large numbers of records in active directory experienced delays of up to an hour of more when the DNS server service in windows 2003 tried to retrieve the data from active directory on restart. How does background zone loading promotes efficiency in the name resolution?
Answer: The zone loading will reduce the time needed to start the DNS server service the impact will probably only be noticeable for very large zones. Explain how DNS has been modified to add support for Ip Version 6 (IPV 6).
A: "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.
The RODC then compares the list of domain controllers that is returned with the list of name server (NS) resource records that it has.
A file-backed DNS zone on such a RODC would be able to accept dynamic updates, as it has a separate database from the domain database. It will only get new data from your main DC and not write new data back to it.
In GNZ, after the creation and enabling of the Global Names zone, the administrators must manually create, add, edit and, if required - delete, name records from that zone. Modifications Necessary to DNS for accomodating Read Only Domain Controllers.
How is it different from the way DNS handles ordinary Domain Controllers?
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. Explain Background Zone Loading Background zone loading is a feature of Windows Server 2008.