You’ve just been handed the responsibility of your church web site and are told to go buy a domain and set up an account on your web host. Or perhaps you know how domain names and web hosts work, in an Microsoft IIS world, but want to add the Apache server to your resume.
In other words, for one reason or another, you want or need to run your personal, church and/or charity websites on LAMP – an acronym for the Linux Apache MySQL Platform. So you take your old PC, burninate some ISO CDs and proceed to set up your own web and DNS servers in the comfort of your basement. Everything is fine until you run headlong into those pesky IP problems.
Now in the past, we’ve talked in detail about some of those wonderful Apache modules such as mod_rewrite. What we haven’t talked too much about is DNS, and acronym for Domain Name Service (or System depending on your religion).
In short, DNS is the way the way the Internet translates human readable domain names such as HealYourChurchWebSite.com, into computer/router a friendly format of 126.96.36.199.
And while DNS isn’t all that hard, it’s hard enough that I would like to recommend to those of you thinking about running a personal development server a fine little article entitled DNS for Novices. As the article’s own description states:
You need this article if you’ve just bought your first domain name or you’re thinking about getting one, and you’re worried that you don’t know enough about the subject. You’re probably asking yourself questions like “Why do I need a domain name?”, “Whose fault is it if it goes wrong?”, “Exactly who am I paying this money to every other year?”. Well. Let’s start with some basics …