Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am a system administrator in a Linux shop. We are in the initial steps of inheriting a Windows Domain. I have some terminology questions:

  1. The usernames are WORKPAC\johndoe. What is the bolded portion called in the username?

  2. The domain name of the Windows Domain is workpac.local. Am I using the correct terminology for that?

share|improve this question
up vote 13 down vote accepted

Yes, the WORKPAC is the domain name. The workpac.local is the fully qualified domain name of the windows domain.

In that domain the PCs would be named something like: PC1.workpac.local

As JoeQwerty pointed out the NETBIOS name does not have to match. The NETBIOS name being the "WORKPAC" part of "WORKPAC\user".

As an example you could have a windows forest like this:

                         /_ \ - WORKPAC.local (forest root/ domain) = Top level

                  /_ \  - CHILD.WORKPAC.local (child domain)

These would be two separate windows domains within the same logical forest. The NETBIOS name for the child domain would be CHILD whereas the FQDN would be CHILD.WORKPAC.local.

For more information on domain structures check out: Active Directory Domain Hierarchy. The article is in reference to Windows 2000 but the same design concepts apply to newer versions. Also check out Active Directory Domain Names. These should get you in the right direction.

share|improve this answer
If the answer to this one is complicated, let me know and I'll just post it as a new question: Does the domain name have to match the left-most label of the FQDN? – Belmin Fernandez Apr 21 '11 at 14:25
The NETBIOS (pre-Windows 2000) domain name does not have to match the DNS (FQDN) domain name... but it usually does – joeqwerty Apr 21 '11 at 14:28
usernames can be expressed as either UPN (eg mel-bin@workpac.local) or legacy, pre-windows 2000 (eg workpac\mel-bin). typically when netbios doesn't match dns it's due to upgrade choices from NT4 – Jim B Apr 21 '11 at 14:55

WORKPAC and workpac.local are both names for the domain. The first one is the pre-Windows 2000 (or NetBIOS) domain name and the other is the DNS (or FQDN) domain name.

share|improve this answer
Thanks for the source Mr. joeqwerty. – Belmin Fernandez Apr 21 '11 at 14:38
Glad to help... – joeqwerty Apr 21 '11 at 14:44

Sometimes when logging into a server, you have to specify the domain with the username. You do this by typing WORKPAC\johndoe or johndoe@WORKPAC.

share|improve this answer

Maybe this can clear things up for you. In windows DOMAIN refers to three things:

1.) The Domain naming context in the Active Directory ldap store. (DC=child,DC=root, --- This follows RFC rfc2247

2.) The kerberos realm that uses the the ldap store. -- realm name is something like principal name is

3.) The DNS domain -- DNS resords for in the typical fashion.

It's best practice (and the default with the GUI based tools) for all of these to match. They don't actually have to. You could add any number of different UPN/SPN suffixes for user/service accounts. The DNS needs to work, meaning that it could be different from all three as long as the SRV records actually resolve correctly.

Anyway, I have found that breaking it down this way usually helps when discussing AD with my UNIX'y brethren.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.