How to name your domain on a win2k3 server?

[felixrosbergen]

Hi All,

I'm installing win2k3 server for my home and it will have the following roles:
- Domain Controller
- File Server
- Print Server
- DNS sever ??? (Do i need this?)
- WINS server??? (Do i need this?)

I have an registerd internet domain that is hosyted by GoDaddy that also has a few e-mail adresses. For the purpose of this disucssions lets called the domain "Mitchell.net" for Pete Mitchell's real last name (Maveric in TopGun).

So Godaddy has my Mitchel.net domain and I have an e-mail adress called [email protected].

I also have a free dyndns account that points a different name, let's called it "Michell.getmyip.com" to my router so i can use the VPN functions on it.

Should the domain name have any relation to any of the above or can i pick any name for the domain? I woud like to name the domain Mitchell.net and then the server ZEUS (since it's the ruler of the house).

Would this cause any problems/conflicts or any kind?

How do i go about using my internet domain name more? For exmaple i woudl like the router to be Router.Mitchell.net. Do i just have GoDaddy make a change like that? It seems that with DynDNS you need to tell them which domain you own or something. I'm a bit lost with this...but since i own it i figured why not use it and not the Michell.getmyip.com one.

Any potential conflicts if i want to run an FTP server, webserver or some other server service on the sever? Would it be access by useing say ftp.zeus.mitchell.net?

Some suggestions to get me in the right direction woudl be much appreciated.

mavric

 

[MikeB]

Hi All,

I'm installing win2k3 server for my home and it will have the following roles:
- Domain Controller
- File Server
- Print Server
- DNS sever ??? (Do i need this?)
- WINS server??? (Do i need this?)

I have an registerd internet domain that is hosyted by GoDaddy that also has a few e-mail adresses. For the purpose of this disucssions lets called the domain "Mitchell.net" for Pete Mitchell's real last name (Maveric in TopGun).

So Godaddy has my Mitchel.net domain and I have an e-mail adress called [email protected].

I also have a free dyndns account that points a different name, let's called it "Michell.getmyip.com" to my router so i can use the VPN functions on it.

Should the domain name have any relation to any of the above or can i pick any name for the domain? I woud like to name the domain Mitchell.net and then the server ZEUS (since it's the ruler of the house).

Would this cause any problems/conflicts or any kind?

How do i go about using my internet domain name more? For exmaple i woudl like the router to be Router.Mitchell.net. Do i just have GoDaddy make a change like that? It seems that with DynDNS you need to tell them which domain you own or something. I'm a bit lost with this...but since i own it i figured why not use it and not the Michell.getmyip.com one.

Any potential conflicts if i want to run an FTP server, webserver or some other server service on the sever? Would it be access by useing say ftp.zeus.mitchell.net?

Some suggestions to get me in the right direction woudl be much appreciated.

mavric

Unless you plan on hosting your own DNS, which I typically wouldn't recommend, you'll want your Windows domain to be DIFFERENT than your public domain. I'd personally use 'mitchell.local'.

You can still host a variety of things on your home LAN/server, but I'd leave your public DNS hosted at Network Solutions/Register.com/whatever.

 

[fcwilt]

Hi

For home use I don't really think you need a domain controller, but that's just me.

I made up a pair of domain names for personal use and treat them as if they were real internet domain names: fam (for family) and per (for personal).

My "rule" for naming a home domain is location.last_name.fam, or in my case sml.wilt.fam. I included location because for awhile I had two homes, the other was nva.wilt.fam.

 

[Lershac]

What you name your domain internally (behind your router) doesnt matter at all, as long as its not a publicly used domain name (suggested to use .local or .fam or some such instead of .com or .net). If you run a mailserver or some such you will plug in your publicly routable domain name into that software.

If you are using an internal domain, YES you need dns, as this is the heart and soul of MS active directory, which will handle all of your authentication and such within your network. It can work without it, but having internal dns set up with correct forwarders will save you tons of authentication problems later when you want to use that. Its not much overhead to run. If you run Microsofts small business server package (SBS) you will definitely need internal DNS.