I know NOTHING about DNS/Name server a crap
I do not know how they work or anything
I want to know how to get ns1.domain.com to host other domains.... how do I do it?

If you do not know how, Thats ok... Thanks for trying
Michael

If you are running WebHosting Manager.
Click on Edit Zone and pick a domain name you want to add the nameservers for.

Now scroll down and put the following entries in:

|__ns___| |___14400__| |_A_| |___IP ADDRESS OF NS1__|
|__ns2___| |___14400__| |_A_| |___IP ADDRESS OF NS2__|

Click Save.

|______| are text boxes.

If you don'thave it but have BIND installed.
Go to /var/named and edit a domain name you want to add the nameservers for.

Add these entries at the buttom.

ns 14400 IN A IP ADDRESS OF NS1
ns2 14400 IN A IP ADDRESS OF NS2

And then restart BIND:

/etc/rc.d/init.d/named restart

Tried to keep it simple.

What are places like http://www.granitecanyon.com/ for?

Temporary name servers (I think?)

Originally posted by smartmlp
What are places like http://www.granitecanyon.com/ for?

The Public DNS Service is a public service provided by Granite Canyon Group, LLC. The Service offers both primary and secondary DNS free of charge to anyone who asks. The Service maintains UPS protected FreeBSD servers that satisfy DNS queries. The servers are geographically separated and all are connected to the Internet via 7x24 dedicated lines with disjoint routes to the Internet's North American backbones.
The Public DNS is useful if you:

Can't get free service from an ISP and don't want to do it yourself
Need secondary DNS servers
Need MX records for a virtual domain
Want control over your DNS records: change DNS frequently, changing ISPs soon
Are inside of a firewall and need publicly-accessible name servers outside of your firewall
Need name servers that are closer to the North American Internet backbones

Originally posted by smartmlp
I want to know how to get ns1.domain.com to host other domains.... how do I do it?

Please explain how/what your situation is for hosting domains now. Do you have an account with a host? A dedicated server? Are a reseller? Etc....

You also have to register a HOST record for the name servers; you can't register a domain to a name server until you've registered the name server itself. This is free with most registrars.

You'll need to go to your registrar for the domain you wish to add name servers for, and find their option to add a "host record", usually under a "Manage" or "Modify" link.

On the server-side, you'll need a DNS server. I personally abhor Bind, and wouldn't use it on my worst enemy's machine. I'd recommend TinyDNS (http://cr.yp.to/djbdns.html) by Dan Bernstein, but that's your choice. Bind (like Sendmail or Windows) seems to be the standard, even though it's not the best tool for the job IMHO.

Regarding your comment about not knowing anything about DNS -- if you are running your own server, I would strongly recommend learning about DNS before offering DNS services to others. Control panels are nice I'm told, but knowing how things work and why is the only way you'll be able to fix problems when they arise. Dan Bernstein (see link above) has some articles on DNS -- an hour or two of your time will better prepare you to offer DNS services to people.

Ok
I have a Windows 200 Server computer, at my house.
I registered my domain at go-daddy

1) I would highly recommend against running a DNS service on a home machine, *especially* running Windows.

2) If you choose to do this anyway, you need 2 IP addresses for the name servers (unless you only want to set up one name server). These must be static IPs. You also need another IP for other internet purposes, though technically it's possible to share one of the name server IPs...

3) Your ISP must allow you to run DNS services from your connection (typically this would require a 'business account'). They also of course must not block incoming requests on port 53.

Assuming you have two static IPs and permission to set this up:

First, you need to point NS1.yourdomain.com and NS2... to your IPs you have set aside. Whoever is currently in charge of your DNS would have to make this change for you.

Second, you need DNS server software on your Windows box. You'll want to search their knowledge base for help, I'm not familiar with doing this under Windows...

Finally, go to godaddy.com and find out how to set up a HOST record for each of your name servers. I've never used godaddy.com so I can't help you with the specifics. Your DNS server will have to already be running on those IPs, and your NS has to resolve there, before you can set up the HOST record.

Again, though, I wouldn't do this on Windows or on a DSL/cable connection -- if you have a dedicated line of some sort (eg, a partial T1), you'll be fine there. Just keep in mind, if Windows goes down, your DNS is out. Most DNS cache's (inappropriately IMO) cache bad DNS entries, which means a short outage can cause a user to be locked out for a while.

Hope this helps, though I'd personally recommend against what you're wanting to do, and instead either get a dedicated *nix box, or use a third party such as GraniteCanyon mentioned above. I also still stand by my recommendation to learn about DNS first -- the above procedure will make a lot more sense to you then.

Or I could use secondary.com

Originally posted by smartmlp
Or I could use secondary.com

waste everyone's time why don't you?