UNIT 2
NT1330
UNIT 2. EXERCISE 1. DNS SCENARIO
It is not required to put a DNS server in such a small location for only five users and snail like network connectivity doesn’t justify the amount of money it would cost to install a server(s) in that area. One exception would be if there is a great amount of file sharing, or other information that would need to be accessed daily by other spots on the network. This sometimes but rarely happens but we could have a situation where we put it in the in the server but we set it up as a secondary or Active Directory Integrated zone type. I recommend installing the servers in the location where you have 30 users and fast internet connection. You could do this also, try storing all the files from either location in the bigger office, and in the smaller location you could remote connect through Virtual Private Network. When we do this all the information from the smaller sight is stored off site. The sight with five users can be run with a cheap router and the server that has thirty users at the office will be set up as the primary zone; since this is utilizing the fast internet connection and has more users this is our MAIN BASE which you can call home. =)
If you were to run Domain Name System on domain controllers there are Active Directory Integrated zones and Active Directory Integrated zones. In classical Domain Name Systems the zone data is stored in text files which sit on the Hard Drive; which of course is protected by New Technology File System. You shouldn’t have the ability to impose per-record security.
You might want to create an Active Directory Integrated zone also; the zone information and the affiliated resource records are imported onto the Active Directory Data Base, NTDS.DIT file. Zones and zone records become objects in Active Directory, which has its ups and it’s down sides, in terms of positive and negative effects. Looking at this from a security perspective, you have the ability to protect the Domain Name
UNIT 2. EXERCISE 1. DNS SCENARIO
It is not required to put a DNS server in such a small location for only five users and snail like network connectivity doesn’t justify the amount of money it would cost to install a server(s) in that area. One exception would be if there is a great amount of file sharing, or other information that would need to be accessed daily by other spots on the network. This sometimes but rarely happens but we could have a situation where we put it in the in the server but we set it up as a secondary or Active Directory Integrated zone type. I recommend installing the servers in the location where you have 30 users and fast internet connection. You could do this also, try storing all the files from either location in the bigger office, and in the smaller location you could remote connect through Virtual Private Network. When we do this all the information from the smaller sight is stored off site. The sight with five users can be run with a cheap router and the server that has thirty users at the office will be set up as the primary zone; since this is utilizing the fast internet connection and has more users this is our MAIN BASE which you can call home. =)
If you were to run Domain Name System on domain controllers there are Active Directory Integrated zones and Active Directory Integrated zones. In classical Domain Name Systems the zone data is stored in text files which sit on the Hard Drive; which of course is protected by New Technology File System. You shouldn’t have the ability to impose per-record security.
You might want to create an Active Directory Integrated zone also; the zone information and the affiliated resource records are imported onto the Active Directory Data Base, NTDS.DIT file. Zones and zone records become objects in Active Directory, which has its ups and it’s down sides, in terms of positive and negative effects. Looking at this from a security perspective, you have the ability to protect the Domain Name