“It seems very pretty,” she said when she had finished it, “but it’s rather hard to understand!” (You see she didn’t like to confess, even to herself, that she couldn’t make it out at all.) “Somehow it seems to fill my head with ideas—only I don’t exactly know what they are!”
If you have been diligently reading each chapter of this book, you’re probably anxious to get a name server running. This chapter is for you. Let’s set up a couple of name servers. Some of you may have read the table of contents and skipped directly to this chapter. (Shame on you!) If you are one of those people who cuts corners, be aware that we may use concepts from earlier chapters and expect you to understand them.
Several factors influence how you should set up your name servers. The biggest factor is what sort of access you have to the Internet: complete access (for example, you can ftp to ftp.uu.net), limited access (limited by a security firewall), or no access at all. This chapter assumes you have complete access. We’ll discuss the other cases in Chapter 14.
In this chapter, we’ll set up two name servers for a fictitious domain as an example for you to follow in setting up your own domain. We’ll cover the topics in this chapter in enough detail for you to get your first two name servers running. Subsequent chapters will fill in the holes and go into greater depth. If you already have your name servers running, skim through this chapter to familiarize yourself with the terms we use or just to verify that you didn’t miss something when you set up your servers.
Our fictitious zone serves a college. Movie University studies all aspects of the film industry and researches novel ways to distribute films. One of our most promising projects is research into using IP as a distribution medium. After visiting our registrar’s web site, we have decided on the domain name movie.edu. A recent grant has enabled us to connect to the Internet.
Movie U. currently has two Ethernets, and we have plans for another network or two. The Ethernets have network addresses 192.249.249/24 and 192.253.253/24. A portion of our host table contains the following entries:
127.0.0.1 localhost # These are our killer machines 18.104.22.168 robocop.movie.edu robocop 22.214.171.124 terminator.movie.edu terminator bigt 126.96.36.199 diehard.movie.edu diehard dh # These machines are in horror(ible) shape and will be replaced # soon. 188.8.131.52 misery.movie.edu misery 184.108.40.206 shining.movie.edu shining 220.127.116.11 carrie.movie.edu carrie # A wormhole is a fictitious phenomenon that instantly transports # space travelers over long distances and is not known to be # stable. The only difference between wormholes and routers is # that routers don't transport packets as instantly--especially # ours. 18.104.22.168 wormhole.movie.edu wormhole wh wh249 22.214.171.124 wormhole.movie.edu wormhole wh wh253
The network is pictured in Figure 4-1.