Running a *.com or *.net from my home machine

[scr0p]

How can I? Lets say I wanted to run the name and server from my box, Apache, Its not possible with windows right? How do I do it with linux? How would I check if its taken or not tho?

[parksie]

You can do it with Windows. But you'd need to leave it on 24/7, so trying to use Windows is probably a no-no

GNU/Linux can serve very well doing that, as can the BSDs. According to all the checking I've done before, OpenBSD is the most secure of the Unix-like systems.

You can run a leaf nameserver off your box if you really wanted to, but I'd leave that to whoever registered your domain name (unless you want to get into some messy paperwork for all the registration stuff).

Apache serves very well, but you need to keep up-to-date with *all* the security patches for your system. A good iptables setup would be a very good idea too.

Technically, the best solution is to have a separate hardware firewall, which is then configured to forward only the necessary ports through for Apache (you should not put what you're securing on the same box that is doing the securing).

[techgnome]

Then you need to get your domain name registered, and linked to your IP address (ask your ISP about this).

[scr0p]

How would I do it within windows? I know I have to leave it on 24/7 and I dont plan on to, I only wanna know because I am curious, I never really wanna do anything in my posts eccept for trying to figure out how/why stuff work, (eccept duel booting linux, I really need to figure that), anyway, as for Apache, yeah I understand, I used to use it to run a small site. I am just wondering how you register a domain name and host it yourself. Thanks.

[agent]

i looked into this.

purchase your domain name (go to internic.net to see if it's avial and for mor info on purchasing)

get an corporate isp account (you need something with a fast upload speed) you'll need at least a T1 line. you also need to purchase a static IP address. when you purchase your domain, you tell it which server it points to, give it your static IP

you'll need some web-serving software, Apache is good, though many sites use MS Internet Information Services (included with windows xp pro and windows 2000) IIS has asp

you may also want to set up an FTP server or Mail Server. IIS can do this, I'm not sure about Apache.

Make absolutly sure that you have a hardware firewall. Please note: HARDWARE. Norton Internet Security will not cut it.

If I missed anything, or you think I don't know what the hell I'm talking about, I invite your comments. I said I looked into this. Never said I actually did it, we're all here to learn... help me to help you...

(OK that's about enough beer for me)

[parksie]

Looks plausible Although after recent events I would have suggested to keep with Apache, and keep an eye on any security patches that come out.

Is a T1 *really* necessary? I can see how it might be, but unless you have high traffic...

[scr0p]

I have this bOok` "Linux unleashed" It seems to have a chapter on setting up FTP, Apache and DNS/NS. when I get up to it ill see how its done in here (long time from now, big book). Thanks for the info agent.

[Yonatan]

Win2k Advanced Server is pretty good.

[Yonatan]

Originally posted by agent
Make absolutly sure that you have a hardware firewall. Please note: HARDWARE. Norton Internet Security will not cut it.

Also note that no matter how good the firewall is and regardless of whether it's software or hardware, it's worthless when misconfigured. Whatever you get, learn to configure it. Very important.

[Zach Elfers]

Originally posted by parksie
You can do it with Windows. But you'd need to leave it on 24/7, so trying to use Windows is probably a no-no

GNU/Linux can serve very well doing that, as can the BSDs. According to all the checking I've done before, OpenBSD is the most secure of the Unix-like systems.

You can run a leaf nameserver off your box if you really wanted to, but I'd leave that to whoever registered your domain name (unless you want to get into some messy paperwork for all the registration stuff).

Apache serves very well, but you need to keep up-to-date with *all* the security patches for your system. A good iptables setup would be a very good idea too.

Technically, the best solution is to have a separate hardware firewall, which is then configured to forward only the necessary ports through for Apache (you should not put what you're securing on the same box that is doing the securing).

You don't need to leave the computer on 24/7. Just whenever you turn it off, visitors would no longer be able to access you're site until you turned it back on.

You can download and Apache or Microsoft server for free on the internet. You need to buy your domain though.

[parksie]

I think if you're planning on having a DNS server on there, eventually the other peering servers will give up being too helpful to yours if it keeps being unreachable. Not 100% sure how the DNS propagation works, but I think it makes a difference.