xxxx.com As Active Directory Domain Ok?

S

Shockey

2[H]4U
Joined
Nov 24, 2008
Messages
2,279
Hello,

I did this without really thinking much about it while following a guide on how to setup Active Directory in server 08. I put xxxx.com as the active directory domain. Is this a security issue with doing this???

If so what should i change it to??

I planning to setup exchange on server08 also.

Thanks in advance.
 
internal network domain names are usually ending with .local, .priv, etc, theres no problem with having a .com domain name for your network, but not everyone does it that way
 
dbwillis said:
internal network domain names are usually ending with .local, .priv, etc, theres no problem with having a .com domain name for your network, but not everyone does it that way
Click to expand...

So if i open up port 80(web traffic) and email ports it won't be of a security risk for AD?
 
I wouldn't want port 80 open/forwarded to my LAN. Too many exploits on it, it'll always be under attack.

The first thing you'll find is, if you host your website or e-mail outside of your LAN....you'll find people who try to hit that from the inside will by default be pointed to your DC..since the DC things www and MX are local. You'd have to create entries in DNS to point those to the public IP of the host.
 
YeOldeStonecat said:
I wouldn't want port 80 open/forwarded to my LAN. Too many exploits on it, it'll always be under attack.
Click to expand...

Ok fair enough. (this is just an experimental lab running on ESX in my garage)

The first thing you'll find is, if you host your website or e-mail outside of your LAN....you'll find people who try to hit that from the inside will by default be pointed to your DC
Click to expand...
So when people on my network (me) request the website xxxx.com they will get my DC instead of the website?

..since the DC things www and MX are local. You'd have to create entries in DNS to point those to the public IP of the host.
Click to expand...

DNS and MX record are way over my head at this point. Working on grasping them next :p
 
Last edited:
It's one of the reasons the convention of .local is usually used.

If you're "stuck" with .com, you can still get around this..make a DNS record for www and point it to your websites server. And make a mail handler record that points to your actual mail host...if you have one. If not...no need to worry.

Since this appears to be a sandbox experiment for you, I see nothing else but a few hours time lost in doing a rebuild. If this was a server put into production with workstations/clients/users already working....it would be a lot of work to do a rebuild. Your call there.
 
You must log in or register to reply here.
Back
Top