Domain models are essential in the management and organization of networks and domain name services. This will help in the planning of future expansion. In networks that will require additional hosts to the network, a proper plan will accommodate additional hosts with ease. This paper will focus on domain recommendations for Alpha Company. The company has five branches and with the need to have internet access in the corporate network.
Choice of the domain model
The choice of the domain model that fits the description is that of single domain model. Since Alpha has the main headquarters that can be used to manage the other five locations, this domain model will fit the infrastructure. In the main domain, there will be the control of all the other domain groups and users. The dual DNS servers will be installed in the main office. This means that the other locations will manage DNS operations from the main office, in San Jose. This arrangement will eliminate the issue of redundancy. There will be one control location of the domains from the main office. It will also be beneficial in terms of availability. This means that there will be high availability of the services in the network. It will also be necessary to install single DNS servers in the remote locations. The remote hosts will query the local DNS sdervers before querying the remote server in the headquarters. This will be used as stand-by when there failure of the dual DNS server in the main office. There are advantages that are associated with this domain model. One of the advantages is that there will be the use of domain controllers as global catalogs. For this case, there will be no need to undertake the plan for server catalog placement. This is because it is available in the system. With this setup, it will be possible to authenticate any user. This will be done by any domain controller in any of the five locations (Holme, Ruest, Ruest, & Kellington, 2011).
Choice of forward and reverse lookup
The most appropriate choice for the lookup choice is that of forward zone. This is the most appropriate choice because there is forward zone where the DNS will resolve the IP addresses for the hostnames that have been given. Since there are many IP addresses which are arranged in subnets, it will be hard to know which hostname has what IP address. This is the typical arrangement in Alpha Company. The DNS will send the IP addresses to the requesters who provide the hostname. Reverse lookup zone will not be possible because it will be hard to have the IP addresses of the hosts. This is because the domain controllers will be stationed in the headquarters (Kelbley, & Sterling, 2010).
There will be a need to have redundant DNS infrastructure because of the breakups that might be experienced in the company. The breakups are possible because DNS users and servers keep on performing lookups on the forest. The disaster of name resolution break will bring harm to the Active Directory functionality (Holme, Ruest, Ruest, & Kellington, 2011).
There will be the need to have a server role that will handle information that is sensitive and private. One of the provisions for this is to have Active Directory Certificate Service. With the installation of this, there will be better management of software licenses that make use of public keys. The network has a provision of sending information that is sensitive over public infrastructure.
Holme, D., Ruest, N., Ruest, D., & Kellington, J. (2011). MCTS self-paced training kit (exam 70-640): configuring Windows server 2008 active directory. Microsoft Press.
Kelbley, J., & Sterling, M. (2010). Windows Server 2008 R2 Hyper-V: Insiders Guide to Microsoft's Hypervisor. John Wiley & Sons.
Windows, H. P. C. (2008). Server 2008. Press Release.