August 2nd, 2003, 10:55 PM
I've finally got a dns server set-up and everything. Now I dont get it... If I wanted say someone has a folder on my server named /folder and their domain name was www.folder.com
what would I do to let them use their domain name instead'a
I have a primary dns set-up for yotokyox.ath.cx and a secondary one too if i need to use it. Just need directions and how to do this.
August 2nd, 2003, 11:24 PM
You need to add a virtual host for their domain. This virtual host will define the folder that acts as root for their website. That's the webserver end of things.
On the DNS server end of things, they need a host. You may offer to host the domain for them. Otherwise, they find their own host or be their own host, and set the 'A' (IP) record for their domain to the address of your webserver.
If you want to host the domain... You'll have to install a dns server, provide a means to let them edit their zone file and a means to dynamically load changed zone files. All they have to do is buy the domain and set the dns registry to use your dns server(s) as the host of their domain.
August 2nd, 2003, 11:53 PM
I'm using virtual host right now on apache but I was wondering if there was another way to do it b/c I hear that u cant use ssl with virtualhost so I'm curious to know how to do it without it.
I have a dns server set-up like i said. And to host their domain I just make a primary or secondary dns?
August 3rd, 2003, 03:41 AM
you'll need either 1 or 2 servers. primary or secondary doesn't have any real meaning. The server with the domain records is the primary or authoritative server. If you should have another server, it will be a slave to the authoritative server.
I don't know about ssl and virtual hosts. There is another alternative though. You can setup a script that'll redirect all requests headed for www.folder.com to the proper url. Something like this:
Browser issues request for: http://www.folder.com
www.folder.com resolves to your server address and would normally result in displaying your root index page. Instead, you have a script handle the root index, and it will return a redirect to the browser...
Server response with: 302 redirect -> http://www.folder.com/folder
Browser then issues request for: http://www.folder.com/folder