Click to See Complete Forum and Search --> : Domain naming schemes
Mountainman
03-26-2001, 01:41 PM
Ok, I am trying to setup everthing for a small personal lan. During setup and subsequent use, I have formed some questions. My first one would be, When naming your domain for a currently non public lan, but will become public eventually in the near future, how do you name your domain? For example, Say I want to call my domain Mountainmancentral. Do I need to add a com or net at the end of that for when I become public or should I do that as default? :confused:
:david:
03-26-2001, 01:46 PM
if you plan to go public, get it right from the start. buy the domain, so that you own it, and start setting up your LAN with that domain name. you should even consider learn BIND so that you can do your own DNS and not have to wait 24 hours or more for someone else to update it.
remember, any services you provide, need to be secure. even if you're doing just a simple ipchains with NAT (ip masquerading) on a firewall/gateway.
Mountainman
03-26-2001, 01:53 PM
thats my plan. I have a dns server setup. I am working on tryingto figure out the jumbled mess that is a mail server. How much is it to buy a domain name? Cash is severely limited (wife has one in the oven). I am trying to figure out a way to afford dsl or cable when they become available in my area in the next several weeks. But, I should go ahead and set it up as mountainmancentral.com? I think that would be about the best course. Thanks!
Infested Flar
03-26-2001, 03:50 PM
Originally posted by Mountainman:
But, I should go ahead and set it up as mountainmancentral.com? I think that would be about the best course. Thanks!
yeah u can. it doesnt matter. what matters is when u get online then. so everything will be setup then.
-flar-
FYI - if you are wanting to register a domain name cheap I use godaddy.com - it's only like $8 for a year.