Tim Cooke wrote:Worst case scenario: Your ISP figures out what you're up to and suspends your service.
Tim Cooke wrote:Of course it's possible. But you seem to be missing / ignoring some important points made by Bear and Ulf.
- If you just want to host a website then your easiest option would be to find a hosting service. It's a lot easier to get going and is much much much much much (yes really that much) more reliable. Also, as mentioned, your domestic ISP contract will most likely prohibit the hosting of websites using your internet connection. (but they have to prove it first)
- If you are just looking to learn about how web server software works, like Apache, Tomcat, PHP, then you can easily do that locally at home within your home network.
My point here is that there are a number of practical and legal difficulties with hosting your own web server at home for public consumption. You need to be very clear on what you hope to get out of this exercise before you dive in. But in any case, here's a checklist of things you need to do to get it working:
1: Turn on your web server
2: Check it's working locally http://localhost/.
3: Check it's working across your own network, from another machine http://<serverip>/.
4: On your router, open port 80
5: On your router, forward port 80 to your <serverip>
6: Check you can access your site from the public internet http://<your_public_ip>/ (this is the IP address assigned to you by your ISP, Google "public ip address")
7: Setup a "static address to dynamic IP" service like dyndns.org or something like that (you may have to pay for this). This will give you a static URL like "williamchaple.dyndns.org" that will resolve to whatever your dynamic IP is at that time.
8: If your router has the feature, configure it to regularly update your dyndns.org account with its current IP address.
9: If your router does not have this feature, configure your server to regularly update dyndns.org with your current IP address. There are free programs that can do this for linux, but it's not hard to write your own script to do it (I know this because I've done it)
10: Check you can access your site through the 'static' dyndns URL
11: Configure your domain nameservers to point to your 'static' dyndns URL
12: Check you can access your site through your domain name.
As you can see there's quite a lot of moving parts to get the whole thing working. It will probably be quite slow and pretty unreliable.
You need to be a bit more specific about how you "want to be able to remote into it"? Do you mean SSH?, FTP?, something else?
I would stress again that you need to be very clear about what you want to achieve by doing this. From experience I can tell you that it's no walk in the park to get working, and at times is just a huge pain in the hole. Let's assume you get it working though. Best case scenario: You sit back and bathe in your own smugness while your friends view your latest "cute cat memes" being served up from the corner of your dining room. Worst case scenario: Your ISP figures out what you're up to and suspends your service.
william chaple wrote:I want the 3 computers to still access the unbuntu desktop using a FQDN like windex.cs.fiu.edu (this is my universities FQDN system unbuntu)
No prison can hold Chairface Chippendale. And on a totally different topic ... my stuff:
free, earth-friendly heat - a kickstarter for putting coin in your pocket while saving the earthhttps://coderanch.com/t/751654/free-earth-friendly-heat-kickstarter