Hmmm... Well it seems I'm finally writing my ISP-howto after all.. in bits
and pieces on a mailing list.
Okay, for the DNS, I configure everything with Linuxconf. You have a nice
X-windows front-end, or you can use the text mode or even HTML for remote
administration.
Simply start Linuxconf, go to Networking, Server Tasks, Domain Name Server
(DNS), and you can configure domains. Just enter a Default IP and you're
set. You'll also have to configure reverse mapping, or ask your upstream
provider to do it.
By the way, Linuxconf has everything you need to configure the mail
server, aliases, add pop accounts for each virtual domain, etc. And
there's on-line help on almost every item, with lots of explanations.
Every user has ftp access by default. The only thing that you need to do
is create a public_html for your users.
Jean-Michel Dault
[EMAIL PROTECTED]
[EMAIL PROTECTED]
On Thu, 1 Jul 1999, root wrote:
> Date: Thu, 1 Jul 1999 23:10:04 -0700
> From: root <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: [expert] cooker
>
> sorry to be a complete pest but how do you add the dns entries, and thanks for
> all the help also what about the ftp access to thier respective domains
>
>
>
>
>
>
> On Thu, 01 Jul 1999, you wrote:
> > It's simple to figure out. I have hundreds of web sites on each of my
> > linux-mandrake servers. Here's how I do it:
> >
> > 1) I create ip aliases in /etc/rc.d/rc.local
> > ifconfig eth0:0 207.253.185.6
> > ...
> > ifconfig eth0:132 207.253.185.253
> > ifconfig eth0:133 207.253.185.254
> >
> > 2) I create "generic" web users. Here's what it looks like in my
> > /etc/passwd:
> > web253:x:625:623:virtual domain whatever.com:/home/web253:/bin/noshell
> > web254:x:626:624:virtual domain whatever.net:/home/web254:/bin/noshell
> >
> > 3) I add virtual domains in apache in /etc/httpd/conf/httpd.conf
> > ...
> > <<VirtualHost 207.253.185.253>
> > ServerAdmin [EMAIL PROTECTED]
> > DocumentRoot /home/web253/public_html
> > #ServerName 207.253.185.253
> > ErrorLog logs/253-error_log
> > TransferLog logs/253-access_log
> > ScriptAlias /cgi-bin/ /home/web253/public_html/cgi-bin/
> > </VirtualHost>
> >
> > <VirtualHost 207.253.185.254>
> > ServerAdmin [EMAIL PROTECTED]
> > DocumentRoot /home/web254/public_html
> > ServerName 207.253.185.254
> > ErrorLog logs/254-error_log
> > TransferLog logs/254-access_log
> > ScriptAlias /cgi-bin/ /home/web254/public_html/cgi-bin/
> > </VirtualHost>
> >
> > 4) I add DNS entries, so that www.whatever.com points to 207.253.185.xxx.
> >
> > Jean-Michel
> >
> >
> > On Thu, 1 Jul 1999, root wrote:
> >
> > > Date: Thu, 1 Jul 1999 14:56:53 -0700
> > > From: root <[EMAIL PROTECTED]>
> > > Reply-To: [EMAIL PROTECTED]
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: [expert] cooker
> > >
> > > On Thu, 01 Jul 1999, you wrote:
> > > > Well, Apache is really easy to setup. You install Mandrake with the
> > > > "Server" option and it installs Apache.
> > > >
> > > > You put your html files in /home/httpd/html and your cgis in
> > > > /home/httpd/cgi-bin.
> > >
> > > What if I wan't to set it up so that user a can ftp into the server and he only
> > > has accesss to his own domain and the other problem is that each domain needs
> > > to have it's own cgi-bin access or is there a better way to do this.
> > >
> > > >
> > > > Apache is pre-configured by default for an ISP environment. It works
> > > > straight out of the box (uh.. rpm). If you want to tweak the
> > > > configuration, you type http://localhost/manual, and you have ALL
> > > > documentation included on your own web server by default. It's only a
> > > > matter of editing the config files, which are plaintext and are full of
> > > > comments. It can't be easier than that, because even with a GUI interface,
> > > > you'll still have to read the documentation to figure out what each
> > > > checkbox does.
> > > >
> > > > Firewalls are a bit harder to configure. You'll have to RTFM a lot before
> > > > you're familiar with the concept. Even me, I have to take a look at the
> > > > man page every time.
> > > >
> > > > Finally, as for dial-up, I don't recommend using Linux as a dial-up
> > > > server. It can be done, but once you have worked with a Lucent
> > > > PortMaster 3, you don't want to go back to anything else.
> > > >
> > > > Jean-Michel Dault
> > > > [EMAIL PROTECTED]
> > > > [EMAIL PROTECTED]
> > > >
> > > > > It will be for both dial up and web hosting there just alot of things that i
> > > > > dont currently use or think about. so far all my experiance has been local
>and
> > > > > not conected to the internet. so there are a few issues to look at. and i
>like
> > > > > apache but it is a bear to set up. i still cant get my cgi scripts to run.
>also
> > > > > i know about next to nothing about firewalls. ihavnt needed them.
> > > > >
> > > > > anyway i can usualy figure things out thats why i was curious about were to
> > > > > find good reading material on the subject. also i mean good and up to date
>that
> > > > > will cover apache setup and security issues also.
> > > > >
> > >
>
