Domain vs domain.com

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am running a 2000 domain with all the service packs.

I was wondering, is there a difference between domain vs. domain.com when
having a work station join the domain?

Regards,
 
Owen@7 said:
I am running a 2000 domain with all the service packs.

I was wondering, is there a difference between domain vs. domain.com when
having a work station join the domain?
Click to expand...

[Assuming the domain is REALLY named Domain.Com ]
there is a slight difference.

With an AD Domain named "Domain.com" the obvious and
default NetBIOS name is just "Domain" -- this name is to
support legacy workstations and allow that the NetBIOS
name can still be used by users to logon as they have always
done under NT domains.

(It also allows for browsing, external trusts and maybe a
dozen, or so, other minor or add-on things to work.)

The machines of a domain should recognize that they are
name fully by their Computer name PLUS the full domain
name: computer.domain.com

They should also recognize their NetBIOS domain name.
 
In
Owen@7 said:
I am running a 2000 domain with all the service packs.

I was wondering, is there a difference between domain vs.
domain.com when having a work station join the domain?
Click to expand...

There is starting at SP4 in Win2k, and all with all XP and Win2k3. These
clients are unable to find domain controllers in a single-label DNS domain
name or register in the single-label domain. You have to make registry
entries to allow this.
300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;300684&sd=RMVP
 
Owen,

Kevin and Herb have answered different questions.

If you are talking about the difference between the single NetBIOS name and
the fully qualified domain name, then look to Herb's response. There is no
real difference when joining a workstation and the NetBIOS domain name is
used for several specific operations.

If you are talking about a Single-label DNS Name -- one where the Fully
qualified domain name is a single label (not .com, .net, .local, .AD, or
anything like that) then look to Kevin's article. This is never a
recommended configuration and should be avoided at all costs anyway.
--
Ryan Hanisco
MCSE, MCDBA
FlagShip Integration Services
Chicago, IL
 
In
Ryan Hanisco said:
Owen,

Kevin and Herb have answered different questions.

If you are talking about the difference between the
single NetBIOS name and the fully qualified domain name,
then look to Herb's response. There is no real
difference when joining a workstation and the NetBIOS
domain name is used for several specific operations.

If you are talking about a Single-label DNS Name -- one
where the Fully qualified domain name is a single label
(not .com, .net, .local, .AD, or anything like that) then
look to Kevin's article. This is never a recommended
configuration and should be avoided at all costs anyway.
Click to expand...

I am assuming, that since he asked the question he must be having trouble
joining clients to the domain. Which is true, if you have a single-label DNS
domain name, you will have trouble.
 
Actually, I can always have the machines join the domain. I noticed that I
have the machine join 'domain'. Later when I go back, it will say that the
machine belongs to 'domain.com'.

I was wondering how this effects the DNS and active directory communicating
back and forth. It seems some machines logon quickly and others take
significantly longer. Any thoughts?
 
In
Owen@7 said:
Actually, I can always have the machines join the domain.
I noticed that I have the machine join 'domain'. Later
when I go back, it will say that the machine belongs to
'domain.com'.

I was wondering how this effects the DNS and active
directory communicating back and forth. It seems some
machines logon quickly and others take significantly
longer. Any thoughts?
Click to expand...

Active Directory uses the DNS name, you are apparently joining the domain
with the NetBIOS name which is fine. After you join though, its domain
membership will show the AD domain name which is the DNS name.
 
Owen@7 said:
Actually, I can always have the machines join the domain. I noticed that I
have the machine join 'domain'. Later when I go back, it will say that the
machine belongs to 'domain.com'.

I was wondering how this effects the DNS and active directory communicating
back and forth. It seems some machines logon quickly and others take
significantly longer. Any thoughts?
Click to expand...

Either name will join (either the NetBIOS name or
the DNS name) and in most cases this will be domain
and domain.com (but this is NOT a guaranteed pattern
as the names might be MyDomain and domain.com.)

BUT as I mentioned in my origianal answer, it is
important that you also add the full domain name to
that machine in the System Control Panel (or equivalent)
and this is best done at the time you join the domain
unless it is already correct.

You want to make sure that the machine ends up with
a full name like:

computer.domain.com.
 
Owen@7 said:
I am running a 2000 domain with all the service packs.

I was wondering, is there a difference between domain vs. domain.com when
having a work station join the domain?

Regards,
Click to expand...

Well, I don't have an official answer, but when joining the domain using
'domain' you are using the NetBIOS name of the domain and then are joining
"NT Style" using WINS, NTLM, etc.

When you specify 'domain.com' then you are using all the cool new AD ways -
DNS, kerberos, ADS, etc.

Just my $0.02... and I have been using the 'domain.com' method ever since I
have been using AD.

AJ Schroeder
 
When you specify 'domain.com' then you are using all the cool new AD
ways -
DNS, kerberos, ADS, etc.

Just my $0.02... and I have been using the 'domain.com' method ever since I
have been using AD.
Click to expand...

I have put in both -- and they both work if you name
resolution works.

Usually I don't bother with the full DNS name since it
is more typing and you might have noticed that I am
typographically-challenged at times.
 
This may seem like an odd question, but keep in mind this is coming from a
DNS n00b.

What if your domain is not registered to your ip? I find it rather confusing
to sign onto 'domain.com' when there really is no .com, just 'domain'.

Nathan
 
Nathan Thomas Sr said:
This may seem like an odd question, but keep in mind this is coming from a
DNS n00b.

What if your domain is not registered to your ip?
Click to expand...

As long as that is a private domain it is irrelevant
(domain.local) etc.

If you are using a registerable name (e.g., domain.com)
then it is practically required that it be registered.
I find it rather confusing
to sign onto 'domain.com' when there really is no .com, just 'domain'.
Click to expand...

You should NOT have a single lable DNS domain name
(which I believe you have indicated you do not.)

EVERY domain has a (sinble lable) NetBIOS version of
the DNS (multi-label) domain name (unless perhaps you
have disabled NetBIOS early on).

All you are doing then is using the NetBIOS version (or
alias) for your domain, e.g., 'DOMAIN' for 'domain.com'.

You may if you prefer login as User:

(e-mail address removed) (the User Principal Name--UPN)*

(*This is the default format but it is possible, especially with
multi-domain forests that the UPN DNS suffix has been altered.)
 
Back
Top