asked on Windows Server 2012 R2 Active Directory Name
I need to setup a new Windows 2012 R2 server for a client. This server will also serve and a AD DC. I want to set the AD Domain name the same as the public website this company owns _ _ _ _ _ _ _ _funeralservice.com (27 characters including .com). This company does not own another public domain name. I know that the NETBION name allows up to 15 characters, and I would like it to match the domain name. What are my options if any?
So if I name the Domain name the same as the public domain name ( _ _ _ _ _ _ _ _funeralservice.com), then the user login will be _ _ _ _ _ _ _ _funeral\User1. I mean this will all work, but its a bit awkward that they do not match. I was just thinking of going with the .local route, but all the articles I have found suggest not doing so. What would be the best resolution? I do not believe the client is willing to purchase another shorter public domain.
Also, should the domain include a subdomain such as internal. _ _ _ _ _ _ _ _funeralservice.com, or LAN. _ _ _ _ _ _ _ _funeralservice.com? I have heard references there is a need to create a subdomain for the the AD domain name to avoid future conflicts. I am not sure about the need to do all of that though. I do not want to complicate things for a very small office network with one or two servers with less than 10 employees. What's your take on all of this?
So if I name the Domain name the same as the public domain name ( _ _ _ _ _ _ _ _funeralservice.com), then the user login will be _ _ _ _ _ _ _ _funeral\User1. I mean this will all work, but its a bit awkward that they do not match. I was just thinking of going with the .local route, but all the articles I have found suggest not doing so. What would be the best resolution? I do not believe the client is willing to purchase another shorter public domain.
Also, should the domain include a subdomain such as internal. _ _ _ _ _ _ _ _funeralservice.com, or LAN. _ _ _ _ _ _ _ _funeralservice.com? I have heard references there is a need to create a subdomain for the the AD domain name to avoid future conflicts. I am not sure about the need to do all of that though. I do not want to complicate things for a very small office network with one or two servers with less than 10 employees. What's your take on all of this?
Windows Server 2012Active DirectoryDNS
Last Comment
cmp119
ASKER
Right now this office does not host their own email, and they currently use an aol.com address. I would like them to upgrade to office365 using their domain name even though its so long. So, I want to ensure I get the domain setup right from the start to anticipate future needs. Feedback is appreciated.
My advice - don't name their AD the same as their public name, unless you are fully prepared to deal with the issues you will face accessing the website from inside the domain. Mostly these manifest when you want to access the website using a URL like "http://xxxxfuneralservice.com". If you only access the website using "http://www.xxxxfuneralservice.com", and the website is never coded to use resources from http://somefuneralservice.com, then you should be fine.
However, to avoid all that, and also handle the name length, I'd suggest making the AD domain a subdomain of "xxxxfuneralservice.com". For example "ad.xxxxfuneralservice.com
However, to avoid all that, and also handle the name length, I'd suggest making the AD domain a subdomain of "xxxxfuneralservice.com". For example "ad.xxxxfuneralservice.com
ASKER
The client always has their website "www._ _ _ _ _ _ _ _funeralservice.com" up and running on their conference room computers. These computers connect to large TVs mounted on walls. So its a definite issue. So you are saying, when I enter the domain name I should enter "ad._ _ _ _ _ _ _ _funeralservice.com"? How will the NetBIOS name appear then? What mean is, how will the user enter the domain to login, ad\User1, ad._ _ _ _ _ _ _ _funeralservice.com\User1.
I am thinking the user would simply enter ad\User1, and this will also address any issues accessing www._ _ _ _ _ _ _ _funeralservice.com from any computer withing the AD domain.
If that is the case, instead of using ad, I will use the owner's initials (JTM) to make is easier and more recognizable to the user should they need to enter a domain name at any point, etc. I suppose this solution will also address any issues if and when implementing hosted O365 email as well. I want to use the same public domain as their email domain instead of @aol.com. I just want to ensure I have everything setup with the internal domain beforehand.
Thank you for your feedback.
I am thinking the user would simply enter ad\User1, and this will also address any issues accessing www._ _ _ _ _ _ _ _funeralservice.com from any computer withing the AD domain.
If that is the case, instead of using ad, I will use the owner's initials (JTM) to make is easier and more recognizable to the user should they need to enter a domain name at any point, etc. I suppose this solution will also address any issues if and when implementing hosted O365 email as well. I want to use the same public domain as their email domain instead of @aol.com. I just want to ensure I have everything setup with the internal domain beforehand.
Thank you for your feedback.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thanks for all your help! I got it all done. No issues discovered!!!