[lug] Website administration book recommendation?

[Glenn Murray]

Much thanks to all who replied.  I didn't know that tummy.com
registered domain names, else I would have recommended it to the
purchaser.  Next time.
 
My understanding now is that somewhere a DNS server known to the
"root" server has a "resource (=zone?) file" which maps the name
reactionxml.org to an IP address of a machine where the web server
runs.  The DNS server with this file is the "authoritative" name
server for the domain name reactionxml.org, and I would put
configuration information into the file.
 
So my problem is to find someone willing to be the authoritative name
server for the domain name reactionxml.org, right?---and then tell
register.com who that is.  Perhaps register.com or tummy .com act as
authoritative name servers as well?  In my case I am on a campus and
am investigating whether the people who administer the campus name
servers will do this for free.
 
But, for curiosity's sake, suppose I wanted to run my own
authoritative DNS; how would I tell the root servers I was the
authoritative DNS and why would they believe me?  There would seem to
be a lot of interaction with register.com.

Thanks again,
Glenn Murray
http://www.mines.edu/~gmurray

On Fri, 4 Jan 2002, Peter Hutnick wrote:
> A little more detail . . .
> 
> First you need to figure out who is going to "host" the DNS for the 
> domain.  That really means running two nameservers (i.e. BIND).  You can 
> run one, and let your ISP run another, or run two yourself, or get your 
> ISP to do both, or get a "hosting service" to do one or both.  Be aware 
> that each nameserver needs a static IP address.
> 
> Then you need to advise your registrar what the nameservers for the 
> domain are.  NSI/Verisign calls this "Domain Hosts" I believe.  I call 
> them authoritative nameservers for the zone.
> 
> Once you have done this, you need to create a zonefile for the . . . 
> zone.  The "domain name" (and hosts) are called a Zone in DNS speak.
> 
> Then you need to point one or more records for that zone to the Apache 
> server.  This system must have a static IP (unless you are using dynamic 
> DNS, but you probably aren't).  You DON'T need an IP for each zone/host 
> UNLESS you want to run HTTPS (secure HTTP).
> 
> 
> Then start reading your Apache book.
> 
> I'd be happy to give you more help off list if you'd like.  My address 
> is phutnick at peakpeak.net.  This list seems to munge the originating 
> address away :-(
> 
> Good luck!
> 
> -Peter
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>