NT1330 DNS Scenario
Course Number – Course Name
NT 1330 – Client Server Networking II
Student Name:
Christian Nelson
Exercise Title:
DNS Scenario
Week Number
#2
Date Of Due Date
April 5, 2014
Date Of Submission
April 5, 2014
Instructor:
Prof. Koneru
DNS Scenario
Establishing an Active Directory integrated zones must be hosted by Domain Controllers and all Active Directory integrated zones are primary zones. Since we are talking about where to place Domain Controllers is not as simple or cut clear but I believe any branch location that’s going to use this service benefits from having a local DC and domain-integrated DNS services. There are some factors in where to place; Domain members rely heavily on DNS services to locate domain resources, over a slow link, the regular activities of authenticating against remote DCs, querying domain resources, and performing other standard DNS lookups can create a sluggish and somewhat bad user experience and finally, if the link between sites goes down and there is no local DNS service, your users won’t be able to browse the Internet unless you’ve configured secondary DNS servers.
For a small branch office with 5 users and a slow link, you might be able to get away without a local DC/DNS server as long as users aren’t dependent on the ability to authenticate against the domain. Non-domain DNS servers are available to service queries in the event your site link goes down. Some DNS-enabled routers can selectively forward requests for select domains to specific DNS servers. This method eliminates the delay of failing over from a primary to secondary DNS servers per client. Maybe A READ ONLY DOMAIN CONTROLLER
For your larger branch office, I would definitely recommend provision the site a local DC/DNS server.
NT 1330 – Client Server Networking II
Student Name:
Christian Nelson
Exercise Title:
DNS Scenario
Week Number
#2
Date Of Due Date
April 5, 2014
Date Of Submission
April 5, 2014
Instructor:
Prof. Koneru
DNS Scenario
Establishing an Active Directory integrated zones must be hosted by Domain Controllers and all Active Directory integrated zones are primary zones. Since we are talking about where to place Domain Controllers is not as simple or cut clear but I believe any branch location that’s going to use this service benefits from having a local DC and domain-integrated DNS services. There are some factors in where to place; Domain members rely heavily on DNS services to locate domain resources, over a slow link, the regular activities of authenticating against remote DCs, querying domain resources, and performing other standard DNS lookups can create a sluggish and somewhat bad user experience and finally, if the link between sites goes down and there is no local DNS service, your users won’t be able to browse the Internet unless you’ve configured secondary DNS servers.
For a small branch office with 5 users and a slow link, you might be able to get away without a local DC/DNS server as long as users aren’t dependent on the ability to authenticate against the domain. Non-domain DNS servers are available to service queries in the event your site link goes down. Some DNS-enabled routers can selectively forward requests for select domains to specific DNS servers. This method eliminates the delay of failing over from a primary to secondary DNS servers per client. Maybe A READ ONLY DOMAIN CONTROLLER
For your larger branch office, I would definitely recommend provision the site a local DC/DNS server.