Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
sorry..and is it also possible for me to register a .com domain name to this webserver even though it has a dynamic public IP. i mean could i use peppie32.dyndns.org (or similar) as a nameserver?
ok...will look into it later. what about what i asked about registering another domain, but using peppie32.dyndns.org (or similar / custom) as a nameserver.
also what version of clamav do you suggest. because if i look at Synaptic dotdeb shows me version 0.90~rc2-1
also what if we cant afford a hardware firewall at the moment...what would be the best software to put in its place?
The only way to get another site working through a router like that is to run it at a different port. The current site is at 8080, so do the next at 8079, and then forward anything hitting the router at 8079 to the separate box. or make apache listen on 2 ports, and anything hitting port A goes to one site, and port B to the other. You can't use domain names in the equation, as the only answer dyndns will give is for peppie32.dyndns.org.
ok that makes sense. and what about the clamav and firewall i was talking about? and how do i add a daemon on? i have a package called ddclient which updates dyndns with my latest public IP. but i want it to run as a daemon so that it does it automatically. but the chkconfig --add ddclient doesnt work
Your firewall is most likely iptables as this is what most distros come with. It is a script that runs at startup.
Code:
chkconfig iptables
will show you if it is on.
Code:
iptables -L
will show you the current configuration. It most likely will require configuration so you want to look into that.
I'm not familiar with clamav relative to web servers so can't help you there.
If it's possible to run ddclient as a service it should say so in the docs that came with it. You could however put it in your boot.local or rc.local startup scripts. The will be under wherever your start scripts are located, usually /etc/init.d.
Quote:
what about what i asked about registering another domain, but using peppie32.dyndns.org (or similar / custom) as a nameserver.
I don't know about a nameserver but if you're asking if you can register two domains that hit the same ip you can. Well at least I do at no-ip which is similar to dyndns. They can all run on the same port and ip as well in apache.
The router simply forwards that port number to the IP address that you told it to. Apache sorts it out as to which server it should use. This is the whole intent of virtual servers.
ok thanks guys...will check out the iptables configuration. and i have sorted out the multiple domains thing. only thing is it only works on port 8080. but thats ok.
thanks everyone for your help and thaks especially to JimBass for taking me through this pretty simple proccess. lol
Yeah, using 2 different domain names would sort things out nicely for apache, then you just need to make apache aware that anything asking for peppie32.dyndns.org goes to one site, and asking for somethingelse.dyndns.org goes to another, or use a totally seperate client, like one dyndns and one no-ip.
IPtables are a fine free firewall software for linux, but having a dedicated box is that much stronger. The box runs all the time, whereas IPtables are a script on a box they are protecting. Far better than nothing, but still not a hardware firewall.
The tools provided by dyndns probably update every 20 minutes or so, you shouldn't need to script them. You could add them to cron if for some reason they don't. You'll also need cron to update the virus database from clamav.
I can't tell you anything about chkconfig, I find rpm distros to be worth less than the blank cdroms they are burnt onto.
You're welcome for the help provided, glad we're able to sort things out.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.