Purpose of the Global Names Zone - Admission/Application Essay Example

DNS Server 2008 Purpose of the Global s Zone Global zone gives a chance to companies of moving to a DNS only environment without the need for a WINS server on the network. When a user makes a request by netbios name by adding the domain suffix and sending it to the DNS server, the DNS server if it hosts the GNZ, it will look in the GNZ first for the name and give response to client as expected. If the name is not located in the GNZ, then the DNS checks an authoritative zone for the name. If the DNS client sends a request without a domain suffix, the DNS will usually not check in the GNZ for resolution.

Read Only Domain Controllers (RODC)RODC was included in the windows 2008 for security reasons as it is not always possible to provide sufficient physical server security in office branches. RODC has read only feature, DNS and password protection, and administrator role separation. DNS should be modified to support the RODC features and capabilities like support of unidirectional replication of AD. The RODC will usually send an LDAP referral response redirecting application requiring write access to active directory to a writable domain controller.

RODC differs from the ordinary domain controllers in that they allow an application requesting write access privileges to write the active directory. The ordinary domain controllers are writable (Sosinsky 84). Background Zone LoadingPreviously, the DNS server would take unnecessarily long duration to load data with extremely large zone stored in the ADS rendering the DNS unable to serve the clients request in a timely fashion. In windows server 2008, DNS loads the zone data from AD while it restarts so as it handle clients’ requests coming from other zones to DNS.

For example if 20 zones are created in DNS and data for two zones have been properly loaded, the server can respond to clients request coming to the first two zones while still loading the data for the other sites. Separate threads perform the task of loading zones therefore the server can respond to queries while still loading the zones (Chellis & Panek 67). How does background zone loading promotes efficiency in the name resolution? When the DNS starts, it enumerates all the zones to be loaded, first loads root hints, and the file based zones, starts responding to DNS queries from the clients computers inclusive of all RPC calls and finally creates separate threads so that DNS queries from clients computers can be served effectively and efficiently.

When a client sends a request for a host in a zone that has already been loaded, DNS replies but if the request is for a zone that has not yet been loaded, the DNS reads zone data from AD and replies (Seguis 333).IP version 4(IPv4) and IPv6 DNS server has been modified in various ways like DNS extensions, software, resolvers and root servers in support of IPv6. In terms of DNS extensions, adopting IPv6 address records (forward lookup) and reverse lookup (ip to name). Forward lookup is resolving from name to IP addresses.

The windows versions has IPv6 enabled by default, unix versions has resolver libraries support for IPv6 and IPv6 resolver will ask for both A & AAAA RRs and try IPv6 first. There is equal number of root servers for both IPv6 and IPv4 (Al-Fayez R., 7). The DNS stores different types of resource records, is independent of the IP version and it is seen as an IP application.IPv4 has 32 bits while Ipv6 has 128 bits with IPv6 having no address mask. The format for IPv4 is nnn.nnn.nnn.nnn, where 0