Your organization opened seven new branch offices in five states. Each branch of
ID: 3854679 • Letter: Y
Question
Your organization opened seven new branch offices in five states. Each branch office has five floors. All of the branch offices use the same Internet domain name. The organization has approximately 25 servers and anticipates that an additional 30 servers should be purchased. The organization is planning to provide network services for about 5,000 users. All users require access to the Internet. Certain resources such as printing and file sharing will be centralized. Individual Project Guidelines Complete the following for this assignment: Using the scenario and assignment information in the Assignment Description, discuss with your group how you should divide the tasks evenly among the members. Perform the following tasks:
Estimate the quantity of connectivity (routers, switches, etc.) devices that will be needed to link all the branches.
Provide your rationale for choosing the quantity of each device.
Estimate the number of Domain Name System (DNS) servers and the type of DNS server that will be installed in each branch.
Recommend the connectivity and bandwidth for each branch, and provide your reasoning behind the recommendation.
Explanation / Answer
ANSWER :
DNS is a really light service. If you were designing this purely as a centralized network setup, as in, all of the remote offices are backhauled to the central office and the central office has the only internet connection, you'd do two DNS servers for the entire organization and be done with it. That would service the entire organization easily, assuming connectivity is up. In that case, I would throw two Linux/windows DNS servers at the main location and set all of your DHCP servers to use those system-wide.
Where the question come in are if you decide to use Active Directory, OR if you want DNS to be highly available. If you start using AD, you'd have a domain controller and a backup at the main site, and at least one domain controller at each other site. Two is technically better, but expensive. This does two things; it allows each office to survive and continue network operations in the event that the links between the two buildings go down. AD controllers are also (normally) DNS servers is smaller organizations, so when you push out the AD servers to each location (which you need to do) you get DNS for 'free' at each location also.
The number of users, at least as far as normal DNS is concerned, doesn't really enter in to play. You'd have to have considerably more than 5000 users on a set of DNS servers for it to be a significant detriment to performance. Availability is really the key.
The "best" answer is two internet facing servers for public .com and .net what ever hosting, and two DNS servers at each location that are internal only. At the main datacenter, you have the master DNS server, and every other DNS server slaves the main zone from that one.
You could also enable DDNS for each location and couple it with the local DHCP servers, so each remote DNS server would be the master for the reverse lookup records on the local subnet. But that's probably a little extreme, since reverse DNS probably doesn't need to be highly available (you can just use the 'real' master DNS server as the master reverse lookup server also.)
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.