VS-ftpd configuration options!

[honey bee]

Hello!

In vsftpd.conf file, we have an option "listen_address" which requires numeric ip-address. If i want to use the site name instead of ip-address what will be the option and how i should implement it?

Thank you in advance !

[redhead]

It dosnt support it, it only supports specific listening ip addresses.
From the FAQ:

Q) Help! Does vsftpd do virtual hosting setups?
A1) Yes. If you integrate vsftpd with xinetd, you can use xinetd to bind to
several different IP addresses. For each IP address, get xinetd to launch
vsftpd with a different config file. This way, you can get different behaviour
per virtual address.
A2) Alternatively, run as many copies as vsftpd as necessary, in standalone
mode. Use "listen_address=x.x.x.x" to set the virtual IP.

And the /usr/share/doc/vsftpd/EXAMPLE/VIRTUAL_HOSTS/README only mentiones IP based virtual hosts.

[honey bee]

Hello!

Thank you for your reply.But the solution you have suggested don't solves the issue becoz at one ip _address i have created multiple sites.Now as the file reads the ip_address and not the site names, so for every site which is accessed through this address, there is one common home directory or you can say home page.So, this is not the correct solution.

Each site has its different home directory, it should land on its home, but due to ip_address based configuartion files it only reads one common home directory for all the sites.

Suggest me any solution which is based on site names and not the ip_addresses.

[Compunuts]

But the solution you have suggested don't solves the issue becoz at one ip _address i have created multiple sites.

FTP protocol doesn't allow to use name based virtual hosting. You can only be used as IP based. So if you have only one IP, then you will only be able to run one FTP.

[flashingcurser]

I think your question is more dns related.

If, for example:

site1.com
site2.com
site3.com

All resolve to your server then there shouldnt be any problem. The only problem would be that you would have to have unique users for each of the domains. "admin@site1.com" = "admin@site2.com" The best way to do that would be using a ftp server with an sql/ldap backend. Walkthrough
That way you would not have to have shell accounts for anyone. In your case, I would also add a table to the database that includes the domain name in case "joe@site1.com" looses his password.

Give read/write permissions only to the users home directory, in this case I assume that to be the root of their site.

The walkthrough above also includes bandwidth limiting to prevent them from becoming uncontrolled porn/warez repositories.




dan

[honey bee]

Hello!

Thanks a lot for your replies

Regards!