Naming domain example.com vs ad.example.com

I am building a new domain from scratch. We own our pulic domain anme example.com. and have publicly hosted website by a third party hosting provider at example.com .  I am being told the new domain name should be ad.example.com or corp.example.com ( subdomain) . My concern is that I don't want users to use subdomain.example.com\username for logging in . There is a point in AD setup that asks for netbios domain name and it does not allow me to use "example" and says is already being used, but it does allow me to use the subdomain name (ie ad. or corp).  I just don't want to instruct users to use subdomain\username to log in to domain.
LVL 1
netcompAsked:
Who is Participating?
 
netcompAuthor Commented:
I much rather do ad.example.com ,but would like to avoid telling users to loginto something funny like AD\username .
During domain install it does not allow me to set the netbois name to "example" to allow my users to do example\username. It tells me that the netbios domain name is in use????Not sure why
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
You can do this either way. You can use ad.example.com and then create another suffix just for example.com. Typically i like to completely have different FQDN's from internal to external.

So for external example.com and internal ambiguous.com. You can do it either way but to ensure that users are not confused I like to completely keep the names separate and not use a sub-domain for internal.

If you have 2 different FQDN one for active directory and one for external all you need to do internally is create a internal zone for example.com and then add any of the websites or other internal services that might have your external domain name used. like your website, if you are hosting it internally.

Will.
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
Typically you would keep the same Netbios name as the FQDN but you do not have to (this is not a best practice though). It is better to keep them the same, if you can.

However, do you have another machine on that network where the machine name is Example?

Setting up a new DC, i have never seen that error message.

Personally i would still not use the same internal FQDN as the external.

Will.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
netcompAuthor Commented:
I think , I found out what is going on. We have an inix ldap server which is doing the job of Active directory and the domain name there is Example.com .Let's say somehow we figure all this out. Can the netbios name be same as domain when using  sub domain i.e ad.example.com ?
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
No it cannot. Netbios Names are flat name spaces which do not have (.) periods in the name.

Will.
0
 
footechCommented:
I think it really is best to keep your NetBIOS domain name the same as the first level of your FQDN.  My preferred choice is to have your internal domain a subdomain of your public domain name.  Both these points reflects Microsoft's current recommendations.

In other words, if public is "example.com", then internal is "whatever.example.com".  Think of alternatives for your domain name like "excorp" (for EXample CORPoration) or some other abbreviation of your public domain or company name to use as the internal.  Once you get used to the idea, I think you'll find it makes a lot of sense is not difficult for users.
0
 
netcompAuthor Commented:
my main concern is where the netbios name come into play  which I guess is at logon. ( or logon to in xP). We also have some mac computers, but I believe they show the domain name at log on if you join to domain.
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
there are several ways to login to a domain. You do not need to just use the NetBIOS name for logon.
examples below...
username@domain.com
domain.com\username
domain\username

Will.
0
 
footechCommented:
And of course in many cases with domain machines, the domain is used automatically.

With our domain-joined Macs you just type in the username and it'll work whether it's a local or domain account.  No need to prepend the domain.
0
 
netcompAuthor Commented:
Thank you all.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.