new project, dnydns basics, etc.?

[bs_texas]

Can somebody give me a quick step-by-step high-level overview?? (not specifics about actually setting up apache, etc., yet)

1. I want to get my own domain, 'www.mybs.net' (for example),
2. Setup a new website and my own email, 'bs@mybs.net', maybe ftp, etc. here on a local machine
3. Make it accessible even though my sbc connection drops occassionally and I get a new dynamic IP each time. I think the Custom DNS package from dyndns.org is supposed to handle that.

I'm just looking for some pointers to get me going in the right direction from anyone who has been-there-done-that. I need the big overview so I can see the general steps I need to take.

I'll be using slackware. I have a DSL connection from SBC Yahoo on a SpeedStream 5100b modem (I have '5260 bridge modem' I could possibly use.). I have a linksys BEFSR41 router. I may possibly setup a machine with smoothwall (just for fun) unless I can talk my CheckPoint contact into giving me a license ;)

So, anybody who has done this sort of thing and can spare a few minutes, I would appreciate it.

Thanks

[JohnT]

Sorry...no time...m/b after my nap.:p

[bs_texas]

nudge.. nudge...

(please ignore the peanut gallery ;) )

[JohnT]

Here's a nut for ya!:p
http://www.siliconvalleyccie.com/index.htm#Website

[bs_texas]

Hey... Thanks for the link. Looks like an interesting site. (Of course, now I have a headache. :D )

I'll browse through that over the next couple of days.

And I'm still open to discussion about this whole concept from others who have hosted their own stuff.

Thanks...

[jme]

I have something similar to what you're thinking about setting up here at home.

I'm sat here on a dynamically assigned IP address (although I have had the same one for over a year now as the modem is never off! ;) ) so I have a www.no-ip.com account which forwards any requests for my domain to my dynamic ip address. If my ip does ever change a small app will update no-ip with the new ip address within 5 mins and their dns servers will then point to the new ip address!

On the server I have apache, proftp and mail servers running with ssh access. All of the packets are forwarded from my smoothwall router to the server which is setup on a DMZ running from the firewall.

I use Debian on the server as it makes updating and installing very simple with apt-get, but with Swaret I would imagine that it will be just as simple to get up and running with slackware. After the install of apache a few choice edits of the httpd.conf (apache's config file - located /etc/apache/httpd.conf in Debian) to load any extra modules that you may want and have installed (php, mysql support etc...) and you're off.

As for the mail server I used the www.qmailrocks.org tutorial which I must say is one of the best tutorials that I have ever used and you end up with all the bells and wistles - pop and imap access, webmail, mailing lists, autoresponders ... etc. As my ISP blocks port 25 (smtp) I had to pay for a mail forwarding account at no-ip which forwards any email to any port that you choose. More info on this here (http://www.no-ip.com/services/mail/reflector).

It has taken a while to get it all working the way that I want, and it was a steep learning curve, but well worth it.

HTH

Jamie

[bs_texas]

Thanks for the additonal input jme.

I also found this:
http://www.dslwebserver.com/

Now I have plenty of info to get started.

At least I got started. I went to dyndns.org and signed up for a domain name and got their CustomDNS service, approximately $36.00 for a year, including the domain registration.

Now, if I just had more hours in a day! I spent yesterday getting my new computer room set up (since the move) and spent most of today installing Windows 2003 Server, SQL, and SharePoint on a test system for work. :eek:

[JohnT]

I also found this:
http://www.dslwebserver.com/ Thats a nice link.....good googling. :D

[bs_texas]

Dang... I've been too busy to get this show on the road. (damn those belgian trappist monks! ;) )

Anyway, I was considering this project again today and was happy to find this quote in httpd.conf:

# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.

woo hoo ...