My next MAJOR project

[kirxklox]

I have this dedicated IP address and want to set up a Tower as a Server. I want to also make the Harddrive a Web Domain that I can use as Data Storage, couple 100 G Bytes.

What do I need to LEARN to do to allow me to do this????????????? :beer:

[ethicaldesign]

Although I haven't needed to do this myself (yet), the process as I understand it is:

Get the server set up and running (if it's a fresh install and you're using linux this will be quite simple by simply choosing to install apache, php, mysql and an ftp server during the install process - I know fedora provides a very easy set up for this but I imagine most linux distributions would aswell).

Then find a dynamic dns service that you're happy with to the map your domain name to your IP (google for 'dynamic dns' and you should find links to sites providing this service.

Register your domain and point the DNS to the numbers/domains that the dynamic dns service specifies.

Then log into the dynamic dns site and set the domain you've just registered (or edited the dns records for if you already have a domain) to point at your static IP that's provided by your host.

Some things to be aware of though:

* Some ISPs aren't keen on you running servers off their connections, so it might be best to check with them that they allow this.
* Some ISPs will block certain incoming ports (port 80 in particular for the http:// access to the web server), so I would check that all ports you need (including email and ftp ports if you want that aswell) are available with the ISP you're using.
* If you're planning to run off an ADSL connection, then the upload speed is usually much lower than the download speed (which is important particularly if you want a number of people to be accessing the site you've set up - their download speed from your site will be limited by the upload speed of the servers connection, and will need to be divided by however many people are using the site).

If you check out some of the dynamic dns sites they should be able to provide you with more detailed information about this. As I say, I don't have first hand experience of this myself running a server off a standard ISP connection (never had a need to), but that's the process basically I think.

[ethicaldesign]

P.S. I forgot to add a point after getting the server up. You'll want to install and configure a firewall on the server aswell (this will be particularly imporatnt if your server is going to be connected to other machines if you have a home network as you don't want it to become a gateway for someone to get into your other machines, not to mention your server itself).

Fedora comes with a firewall option as part of the installation I believe, and is pretty easy to configure. There are other firewall options for linux aswell that might be worth considering. If you read the documentation for whatever firewall you choose it should explain how to configure it for server use in detail.

Good Luck.:)

[ethicaldesign]

P.P.S. Another option might be to set up your own DNS on the server itself and just put the IPs for that into the domain record directly (You'd need to create nameservers for the domain with your registrar aswell as pointing the domain to those nameservers). I think you'll need 2 IPs for that however, though you can probably ask your ISP about that (some will offer an extra IP for a small aditional cost I think).

The reason I suggest using a dynamic dns service is that it should be very easy to change quickly if you move ISPs at any point or your static IP address changes, meaning you don't have to wait for changes to your domain record itself to propagate, avoiding downtime (as long as the dynamic dns service you're using is reliable).

It would also save you having to fuss over setting up the DNS service on your box, and you probably won't need 2 IPs (you may very well be able to get away with using only 1 IP for the DNS but I'm not sure about that).

As I say, I haven't done this myself yet, and haven't researched it yet so can't be 100% sure but I think that's how it would work. Hopefully someone else here who's running a ded server can pipe up and help :)

[ethicaldesign]

Ah...Also forgot to mention:

If this is just for your own personal use, I believe you should be able to access the machine by just using the IP address instead of the domain name, saving all of the hastle with setting up DNS records etc.

In that case you'd just set up the server, then when you want to access it use:

http://0.0.0.0

where (0.0.0.0 - is replaced with your IP address).

[Jamie]

I have heard good things about http://www.no-ip.com/ for dynamic dns.

[the_pm]

Also, make sure you keep current with OS security patches to prevent your system from being compromised. A RAID configuration would be most helpful as well, since your hard drives will be in constant use and if your server HD wears down, you may lose every last bit of data on it.

I've considered hosting for myself off a dedicated line and IP before, and given the small expense associated with letting professional network admins handle the job instead, I've always opted to let them do what they do best. But if you're willing to put the time and money into making it happen, by all means go for it!

[kirxklox]

No PROBLEMS so far. The TWO Static IPs are available. 640/640 MB up and down with more available on DSL.

[kirxklox]

This is primarily a Data Retrieval System. I will be using High End Service for the Major Domains.

Picture Files, PPT, PDF, flash and others will be the major inputs.

[Tjobbe]

Good luck, let us know when its all up and running.. are you using linux or windows?

[kirxklox]

I do not know yet. Depends upon the cost and the learning curve.

[Marble]

I have run servers from home quite a bit... I had several from a while until we moved to a small apartment and my servers went bye bye... so now its one computer and a firewall (that is sitting in the corner un used until I have time to set it up again..)

But viewing what you want to do:

1. No matter what - put it behind a dedicated firewall. Relying on the firewall from the OS that the webserver is installed on is not the best idea. Use both..
If you want something simple - get an old box (p2 etc..) and install either one of those tiny linux distros (like Smoothwall) for a firewall or (my personal favorite) m0n0wall.. which is from FreeBSD... If you want to tackle a beast you can install OpenBSD...

2. Keep the server off the same network as your internal network.. Ideally put them on different IP blocks and seperate your lan with a router and deny all access from outside to your lan... just keep the server in the DMZ..

3. I am all for using FreeBSD as a server as its more mature to maintain than most linux distros and to run it lighweight without a GUI is a breeze... The 5.3 series comes with PF - which is OpenBSD's packet filtering system - regarded as the best firewall of any system... But installing Fedora or something like that will be easier - initially... But I am telling you FreeBSD is really EASY to maintain once you *get it*...

[kirxklox]

I have to have access from a remote location. Seems it will be several hundred miles away. :banana:

[Marble]

Ah.. so you are getting a dedicated server at a datacenter? Is it managed at all?

[kirxklox]

No, that is not what I said. I stated the server is several hundred miles away. I will be operating it by remote. Did not say anything about its location. Probably in a damp, dungy old basement. :lol:

[Marble]

Muhahaha.... are you planning to overthrow the world!

[kirxklox]

No, just starting a Coup-De-Tat amongst friends. :lol: