Domain Name System ( DNS ) zones can hive away in sphere and application directory dividers in Active Directory Service ( AD DS ) .AD DS information construction have a divider that can separate informations for different reproduction intent.
Zone reproduction Scopess have different type. There are Zone reproduction Scopess to all DNS waiters in this wood, Zone reproduction Scopess to all DNS waiters in this sphere, Zone reproduction Scopess to all sphere accountants in this sphere and Zone reproduction scopes all sphere accountants in a specified application directory divider.
Zone reproduction range to all DNS waiters in this wood. Windows Server 2003 and Windows Server 2008 sphere accountants have replicated zone informations will running the DNS Server service in the AD DS forest. Replicates zone information to the ForestDNSZones divider so it provides broadest reproduction range.
Zone reproduction range to all DNS waiters in this sphere. Replication zone informations in all Windows Server 2003 and Windows Server 2008 sphere accountant will running the DNS Server service in Active Directory Domain.
This reproduction will retroflex zone informations to the DomainDNSZone divider which was the default puting for DNS zone reproduction.
Zone reproduction range to all sphere accountants in this sphere. Replication zone informations to all sphere accountants merely exist in Active Directory sphere. If we like to puting others window like Windows 2000 DNS waiters to lade an Active Directory-integrated zone.
Zone reproduction range for all sphere accountants in a specified application divider. This zone reproduction range will retroflex zone informations based in the reproduction range of the specified application directory divider.
Application directory divider is non replicated to the planetary catalog for the forest if AD Ds-integrated DNS zone information is stored. While AD DS-integrated DNS zone that stored in a sphere divider is replicated to all sphere accountants in AD DS sphere. This part of informations will hive away in planetary catalog.
Active Directory Domain Service ( AD DS ) will supply an enterprise-level tool for forming, turn uping resource and managing in a web. Integration of DNS service is separated into two portion.That is design and execution of Active Directory Domain Service ( AD DS ) .
We need to see the undermentioned measure when we would wish to deploy Domain Name System ( DNS ) waiters with AD DS.
We need to do certain that DNS is located for turn uping sphere controllers.DNS waiter provides enrollment of sphere accountants in DNS sphere namespace which service provide by Net Logon.
AD DS usage by Window Server 2003 or Window Server 2008 which running by DNS waiters. Integrating of AD DS can take advantage about DNS characteristic such as AD DS reproduction, record ripening and scavenging and unafraid dynamic update
How DNS integrates with AD DS
We can advance waiter for function of a sphere accountant for a specified sphere. We can stipulate a DNS sphere name for AD DS sphere. We can execute this action by waiter that fall ining and advance waiter and put in DNS Server function is the option given. The DNS Server function provided because DNS waiter required for locate this waiter or member of AD DS for others domain accountant. Primary zones merely can be stored in directory.DNS waiter can non hive away secondary zone in directory which must hive away in standard text files.When all zones store in AD DS, multimaster reproduction theoretical account will take the demand of secondary zones.
Benefits of AD DS integrating
Multimaster informations reproduction and enhanced security which is DNS characteristic will establish on the capablenesss of AD DS. Single-master update theoretical account will find the conducted of DNS update. Single-master update theoretical account individual important DNS waiter is designed as primary beginning for a zone. Master transcript of the zone is in local file. Single fixed point of failure is a primary waiter for a zone. Update petition for DNS client will non processed for a zone if this waiter is non available.AD DS reproduction mean that dynamic update of DNS will direct to any AD DS-integrated DNS waiter and will replicated to all others AD DS integrated. The zone can be update by the DNS operating at any sphere accountant because it is to the full replicated to all sphere accountants. Any primary waiter can treat petition from DNS client to update the zone with multimaster update theoretical account of AD DS. We can procure dnsZone by use entree control list ( ACL ) .
When a zone is added to AD DS sphere, this zone will automatic to retroflex and synchronise to new sphere accountant. DNS server service can be selectively removed from a sphere accountant but the directory-integrated zone is stored at each sphere accountant. So, zone storage and direction is non a extra resource. Besides that, the method usage to synchronise directory-store information offer public presentation betterment over standard zone update method.
We can streamline database reproduction planning for web with incorporating storage of DNS zone database. We must be after and give administer when we separated and hive away our DNS namespace and AD DS sphere.
Standard DNS reproduction is less fast and efficient than Directory-integrated reproduction. Directory-stored zones need less informations to be used because AD DS reproduction processing is performed on relevant alterations merely.
When we need to partition our namespace into zones, we have to reexamine the traffic form in current and proposed web. We can utilize DNS waiter to reexamine the DNS waiter satisfies and DNS public presentation counters which provide by System Monitor. Traffic routing consists of Server-to-server traffic and Client-to-Server traffic. Server-to-server traffic can happen when zone transportation with others DNS waiter and by DNS interoperability with others server. While, Client-to-server traffic is caused by DNS client computing machine send question burden and dynamic update. This traffic will besides happen when DHCP server supplying update for earlier-version DNS that will non back up dynamic update.
Besides that, analysis size of the web and estimation traffic form.
Examples like big web, we have to analyze, trial, revision and analysis, after that we can partition and depute DNS zones based on demand which have to supplying efficient and fault-tolerant name service for each site.
After the analysis, we can do the decision about divider and depute the DNS Zones based on the demands for ground of supplying efficient and fault-tolerant name service of each location or site.
DNS Server service support incremental zone transportation that allows waiter and waiter to retroflex a standard zone. This map can cut down DNS reproduction traffic for reappraisal zone planning.
Sphere or application directory divider of Activity Directory Domain Service ( AD DS ) uses to hive away the Domain Name System ( DNS ) zone. We can partition to separate informations for different reproduction intent which is a information construction.
Command for create DNS application directory divider.
Open a bid prompt.
Type “ dnscmd & lt ; ServerName & gt ; /CreateDirectoryPartition & lt ; FQDN & gt ; ” .
Use to stipulate the name of the command-line tool for pull offing DNS waiter.
& lt ; ServerName & gt ;
Is required to stipulate the DNS host name of the DNS waiter.
Is required for create a DNS application directory divider.
& lt ; FQDN & gt ;
Is required for stipulate the name of new DNS application directory divider.
We can see the complete sentence structure for this bid by typing
“ Dnscmd/CreateDirectoryPartition/ ? ”
We can open bid prompt runs as decision maker by chink on start choose all plan after that chink accoutrements.After that right click the bid prompt and runs as decision maker.
Enlist a DNS Server in a DNS Application Directory Partition
We have to enlist the DNS waiter that hosts the zone in the application directory divider after we create a Domain Name System ( DNS ) application directory divider to hive away a zone.
We can hold the below measure to enlist a DNS waiter in a DNS application directory divider
We have to open a bid prompt.
After that type “ dnscmd & lt ; ServerName & gt ; /EnlistDirectoryPartition & lt ; FQDN & gt ; ” .
The proposes of DNS Notify is master waiter for a zone notify certain secondary waiters in that zone that alteration and secondary waiter will look into whether demand to originate zone transportation which is alteration to the DNS criterion ( RFC 1996 ) .
Notify list demand to find which of the secondary waiter in zone demand to direct the alterations to the maestro waiter. Notify list is a list of the IP references for those secondary waiters.
If local zone on maestro waiter update, the consecutive figure in SOA record is updated to stand for new version of zone.After that, maestro waiter will direct notify message to others server.Then, all secondary waiters for the zone will have notify message.This message is respond by initialing on SOA-type question back to the notifying maestro waiter. This message will find if zone of the notifying waiter is a ulterior version that shop in zone. The notified waiter will bespeak for AXFP or IXFR zone transportation if consecutive figure used in SOA record of the zone advising waiter is higher than consecutive figure used in SOA that current transcript.
User more frequently holding the job of holding job related to zone transportation, broken on zone deputation, resource record is disappeared in a zone hosted on a secondary DNS waiter and different zone job.
If the user holding the job related to zone transportation. This job is cause by the DNS Server Service is stopped. We can work out the job by verify maestro and secondary DNS waiter. If the job cause by DNS do non hold web connectivity during transportation. We can extinguish the possibility basic web connectivity job between two waiters. Besides that, this job besides can do by consecutive figure is same at both beginning and finish. We can utilize DNS director to increase value of consecutive figure to greater value at the secondary waiter.
Second job, user utilizing zone deputation but broken.This job cause by zone deputation is non configured right. User has to revise the zone constellation and reconfiguration the zone deputations. Zones are a topographic point that contain information about DNS spheres and bomber spheres. Single-node database is a default zone original for a DNS sphere. Subdomain is added straight to its parent and stored as individual zone. A subdomain that remains its portion with same zone, they besides call as subzone. When have subzone, new subdomain will retained as portion of the zone.It will retroflex and update along with the zone individual entity. Besides that m we besides can depute subdomain off and pull off them in their ain zone. Parent zone have to deputation record for those subdomain that delegated to its ain zone.
Third job is resource record is disappeared in secondary DNS waiter. This job cause by DNS waiter is unable to serve incremental zone transportation from the petition of a secondary DNS server.Primary DNS waiter will response to a full zone transfer.When this job occurs, some of the record in secondary zone can be deleted. We can work out this job by utilizing hotfix.