Choosing AD Domain Names
I have read enough about AD Domain Name selection and see that company.local is a bad idea.
Alternately, it appears that something like corp.company.com is recommended where company.com is registered.
In the case I'm considering, company.com is in use in the outside world. www.company.com is being redirected to www.company2.com.
So, I understand that I'd choose something like corp.company.com or btfsplk.company.com, etc.
If this is done, is there any particular concern that there could be conflict between www.company.com and btfsplk.company.com if we misconfigure something internally?
If so, I'd be motivated to register btfsplk.com and just use it internally only so there can be no conflict for sure.
Or, would that be overkill?
Alternately, it appears that something like corp.company.com is recommended where company.com is registered.
In the case I'm considering, company.com is in use in the outside world. www.company.com is being redirected to www.company2.com.
So, I understand that I'd choose something like corp.company.com or btfsplk.company.com, etc.
If this is done, is there any particular concern that there could be conflict between www.company.com and btfsplk.company.com if we misconfigure something internally?
If so, I'd be motivated to register btfsplk.com and just use it internally only so there can be no conflict for sure.
Or, would that be overkill?
You can have company.com internally and externally as well
U need to be careful and ensure that company.com is free and not occupied by somebody else
You have to work with internal and external dns servers and only liberty you lose is to access "company.com" as website url from intranet
You need to use www.company.com or any other subdomain you like. This is because company.com is resolved to domain controllers internally
Apart from I don't see any issue with that
Else, you can use .local internally and .com externally
There is no bad in that as well as long as you configure your dns correctly
U need to be careful and ensure that company.com is free and not occupied by somebody else
You have to work with internal and external dns servers and only liberty you lose is to access "company.com" as website url from intranet
You need to use www.company.com or any other subdomain you like. This is because company.com is resolved to domain controllers internally
Apart from I don't see any issue with that
Else, you can use .local internally and .com externally
There is no bad in that as well as long as you configure your dns correctly
ASKER
Mahesh: Really, that was the point of my question. "no bad in that as long as you configure your dns correctly". But, what if we don't do "everything correctly" on the inside?
Let me be clearer about this:
*We* are using registered company.com and www.company.com in the outside world and don't intend to change that. It's being managed for us by others.
We are not planning to use *just* company.com or www.company.com on the inside.
However, we *are* planning to use corp.company.com on the inside.
The question is:
Can we do that with NO concern that our inside activities might mess up the outside world operations?
The alternative would seem to be to get another public domain name and only use it on the inside (for now at least).
Let me be clearer about this:
*We* are using registered company.com and www.company.com in the outside world and don't intend to change that. It's being managed for us by others.
We are not planning to use *just* company.com or www.company.com on the inside.
However, we *are* planning to use corp.company.com on the inside.
The question is:
Can we do that with NO concern that our inside activities might mess up the outside world operations?
The alternative would seem to be to get another public domain name and only use it on the inside (for now at least).
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks all!!
Mahesh: Really, that was the point of my question. "no bad in that as long as you configure your dns correctly". But, what if we don't do "everything correctly" on the inside?
In case of DNS, its must be configured correctly otherwise it will start breaking things no matter how simple or how complicated name space design you have.
U don't have liberty to say "But, what if we don't do "everything correctly" on the inside?" - At least in case of DNS
Personally I would avoid corp.company.com as I don't see any benefit with extra subdomain in root domain it self though it don't have any issues
Instead I prefer company.com or company.local internally and company.com externally
for www (your website) it depends if it is internally or externally hosted and no entry in your local dns
an external cname www.company.com www.company2.com will cause an ssl mismatch error unless the SAN of the certificate has both www.company.com and www.company2.com
no need to register a subdomain for a domain that you own as you are authoritative for any *.company.com or *.*.company.com
if you make an error in your local dns it won't affect your remote users accessing your www.company.com since they don't access your local dns unless your local dns and name servers are externally accessible.