Subtitles of the Movie

Now as we conclude chapter 1 here and before we launch in to our discussion of TCP/IP, we want to continue to lay the groundwork by discussing the planning of your domain names and also the planning of zone files, and differentiate between the two here. When you plan your domain names you must use a unique domain in the parent level Namespace. Then after you plan the domain you need to select the name server that will be authoritative for that domain space. So in other words, the name server that will hold the zone file that's authoritative for the domain space. On my Paint pad here and I'll use this throughout the course, I've scribbled down as best I can with my mouse, the representation of the DNS domain space starting with the root level Namespace com, and then here, I have to check if I want to use beanlake.com I have to check in the parent level Namespace, to make sure that the domain name is unique, Then once I‘ve done that I want to select the server, the name server that will hold the zone file that's authoritative for that domain space. I also maybe want to decide what Namespace I want to use for my Active Directory Namespace because the Active Directory Namespace uses DNS Namespace for resolving names. So I need to keep that consideration in the back of my mind because typically with Server 2003 eventually you're going to be implementing Active Directory. When you implement Active Directory, you have three naming choices you can either use the same Namespace as the existing public Namespace. So if this step is being taken care of you might want to decide to make beanlake your Active Directory Namespace as well as your public Namespace. So you have FTP server, then you have your name server and then you have client and you have domain controllers all in this single Namespace. You might want to use a child domain for Active Directory Namespace. In this case you would leave certain public resources in the beanlake domain and have a child domain, say corp that you use for the Active Directory Namespace, or as the root of your Active Directory forest that's another choice you have. The 3rd choice you have is that you can use separate public and private Namespaces and when you do this, you can just implement Active Directory in any old Namespace you want to, as long as it conforms to DNS naming conventions and this one does, beanlake.bc. In this case this would also be the root of the DNS Namespace and then you can continue to build domains, child domains again using DNS conventions. In this case you would need to configure your name servers to refer requests to the public Namespace, to other name servers because these name servers in the active directory Namespace would not be able to resolve things like ebay.com or vtc.com. So these are just essentially your 3 choices you have. When you implement DNS and your Namespaces you also implement zones and a zone represents the physical division of the domain space. Your zones are where the resource records are stored. Zones can be described as being authoritative for portions of the domain space and it can be a single domain or many domains. So if I have a, lets say another child domain of bean lake and I want to call this one, oh let's just say kc, I can have a zone stored here. This is a zone and it can be authoritative for both the beanlake.com and the corp.beanlake.com, domains. I can create another name server here and on that name server I have a zone file and that zone file is authoritative for only a single portion of the DNS Namespace. thekansascity.beanlake.com Namespace. So this is an important distinction to make and one that will certainly serve you well if you can make it now before we get to the chapter where we actually configure DNS. Being able to differentiate between the DNS Namespace, the Active Directory Namespace which is built on the DNS Namespace, and then finally your zones which are the physical manifestations of the DNS Namespace, where the records are kept themselves in either sometimes the Active Directory database or in just regular old text files. But these contain the records that map ftp.beanlake.com to an IP address and the domain controller for beanlake.com to an IP address and so on and so on. Zones can be authoritative for multiple portions or they can be authoritative for just a single portion of the DNS Namespace. The purpose of all these things is to facilitate network communication for humans to resolve names to IP addresses. And in the next chapter here we talk all about the IP address and how it's crucial for today's networking communication.