[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] Where are the RaQ gurus?

At 02:37 PM 2/12/00 -0600, you wrote:

I've heard of the gurus... Where are they? Does someone know of a source
of people that can setup a raq?
Here (whispers Jeff, tentatively holding up his hand <smile>). If you're looking for a consultant, please let me know offlist. 


All I need is a simple setup of my new raq3 for dns, email and hosting
multiple name based domains on a single ip.


Sounds simple enough.


Our co-location facility has allocated 8 ips for our use.


More than enough.


The first ip (216.149.220.98) was used for the machine's ip. Our domain
sitepresence.com is resolved through our colocation facility's dns
server to this ip.
Here's exactly what 9Net Avenue has set up for you, as returned by their nameserver, <ns2.9netavenue.net>: 


sitepresence.com
        origin = ns2.9netave.com
        mail addr = hostmaster.9netave.com
        serial = 2000020815
        refresh = 28800 (8H)
        retry   = 7200 (2H)
        expire  = 604800 (1W)
        minimum ttl = 86400 (1D)
sitepresence.com        nameserver = ns2.9netave.com
sitepresence.com        nameserver = ns3.9netave.com
sitepresence.com        preference = 10, mail exchanger = sitepresence.com
sitepresence.com        internet address = 216.149.220.98
sitepresence.com        nameserver = ns2.9netave.com
sitepresence.com        nameserver = ns3.9netave.com
ns2.9netave.com internet address = 216.156.2.2
ns3.9netave.com internet address = 216.156.2.3
sitepresence.com        internet address = 216.149.220.98
Looks good, except that I'd set up "mail.sitepresence.com" as your mail exchanger. There's already a CNAME record for mail.sitepresence.com; it points to sitepresence.com. 


Now I want to setup the following:
"www.sitepresence.com" for http access,
There's already a CNAME record for www.sitepresence.com; it should work out of the box. Do you know how to set up the gui interface, or are you looking for someone to do it for you? Do you have website, or are you looking for someone to do one for you?
When I try to go to <www.sitepresence.com> with my browser, I end up getting redirected to <ns0.sitepresence.com>, and get a 430 unable to resolve domain name error. Both your "box" and your DNS need some work. It's set up with a hostname of <ns0.sitepresence.com> and there's NO DNS for that hostname. 


"sitepresence.com" for email access,
I presume you mean "name@xxxxxxxxxxxxxxxx"; that's easy enough to do from the gui interface, too. Your box IS SMTP on port 25, so the first step is already working correctly. 


"ns0.sitepresence.com" for the primary dns server,
"ns1.sitepresence.com" for the secondary dns server,
Your box is already answering DNS service at the IP# for your box, but there's no DNS set up for either of these addresses, so nothing can find these addresses. 


Question 1: < which type of record do I create for each? >
Isn't that a bit beyond the scope of a mailing list? Do you really need someone to set this box up for you? That's what we and others do (consulting) for a living, you know. 


Question 2: < what do I name the cobalt machine? >
If you're going to use the primary IP# for hosting your own site (I don't), I'd name it "www". That way you won't have to disable rewriting headers in the httpd.conf file, to keep everyone's browser from rewriting whatever's typed in to the confusing "ns0.webpresence.com". 


Question 3: < which ones need a dedicated ip address?,
Which of what needs a dedicated IP address? Actually you can run the whole box off one IP address as long as no-one needs either anonymous FTP or an SSL certificate. 


and do I need to
notify the colocation facilty to tell them what I name them?>
Only if they're going to administering something in your system in such way, or if they require it under contract. If you were colocating with us, we wouldn't care, unless we were administering your box for you under contract. 


Question 4: < As I understand it My provider's dns will point
sitepresence.com to our primary ip (216.149.220.98) Then as we setup new
name based domains all pointing to a single ip our name servers will
resolve the domain requests -- Is this correct? >
It certainly could be set up this way. But I get the impression you've only got one name-server. Setting up two virtual nameservers to point to the same physical box is a no-no. I leave it to some observant readers of some of my (and other learned scholars' <grin>) previous posts to explain why, or you may read the archives. You really need an offsite secondary. 


Thanks,
Robert Hughes


You're welcome, Robert.
If there's anything further I can help you with, please contact me on-list or offlist. 

Jeff

--
Jeff Lasman <jblists@xxxxxxxxxxxxx>