FQDN

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

Guest

Hi,

I was discussing with a partner who works in the Linux area who ask me what
does is the reason to use the FQDN to the domain like = "contoso.lan"
instead of just contoso without the second level domain ".lan" he said that I
don't need the full fqdn like = pc.contoso.lan just to use pc.contoso, well
according what I been reading Microsoft along all the articles that i found
always the right syntax is for instance hi.contoso.lan NOT without lan i
woulk like to understand the main reason to use the structure how Microsoft
said. Just to discard my partner's argument and understand better the
situation.

Thanks for your comments !!
Thanks for your comments !!
 
AD domains follow the naming convention of DNS names. So if your company is
called somecompany and has a internet presence called somecompany.com
several possibilities exist in naming the AD on the internal network. It
could be something like:
* somecompany.com
* somecompany.local
* <something>.somecompany.com (while <something> = AD or internal or infra
or whatever)
* internalinfra.com
* internalinfra.local

all of these names are NON-SINGLE LABELED DNS NAMES

Although single labeled DNS names (e.g. company) are supported, they are NOT
recommended! Why? Single labeled domain names required additional
configurations and in time it might even give you headaches.
Read more in: MS-KBQ300684_Information about configuring Windows for domains
with single-label DNS names
Quick tip about single labeled domain names: DON'T DO IT!

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto #
BLOG --> http://blogs.dirteam.com/blogs/jorge/default.aspx
 
Don't confuse AD domain names with DNS names, they are not necessarily the same
though they often are.

I think your partner is thinking about domain name suffix completion, that is
fine for normal DNS resolution but may not work for domain functions.

joe
 
Misaro said:
Hi,

I was discussing with a partner who works in the Linux area who ask me
what
does is the reason to use the FQDN to the domain like = "contoso.lan"
instead of just contoso without the second level domain ".lan" he said
that I
don't need the full fqdn like = pc.contoso.lan just to use pc.contoso,
well
according what I been reading Microsoft along all the articles that i
found
always the right syntax is for instance hi.contoso.lan NOT without lan i
woulk like to understand the main reason to use the structure how
Microsoft
said. Just to discard my partner's argument and understand better the
situation.
Click to expand...

The DNS name of the domain IS the full name, whatever that
happens to be. It is also possible to use a partial name and
depend on the client OS to append the parent or other suffixes
but this is NOT always guaranteed to work.

It is also possible to use the NetBIOS (version) of the domain
name for some purposes; this is included primarily for legacy
support but works nonetheless.

Also, technically a FQDN is ONLY one which includes a
"terminating dot", i.e., contoso.lan. or www.microsoft.com.

Without that dot on the end it is NOT "Fully Qualified" but
merely a DNS name.
 
Back
Top