DOMAIN NAME

Hello

Setup a Windows 2003 server on a domain with .local namespace and a 18
character domain name i.e artisticupholstery.local

When users log onto the domain they will only see 'artisticupholst' as the
domain name. Will this cause any problems?

Everything appears fine elsewhere.

Kind regards,
Jeff Lee

By default, Windows truncates the domain name to include only the actual
domain name when viewed in the log on screen. Thus, "mycompany.local"
becomes "MYCOMPANY" OR "it.mycompany.local" becomes "IT" or "MYCOMPANY" (both
options are visible). When you perform pings however, the machine will
automatically add the entire DNS name. Thus, if you ping computer1, the
machine will resolve the IP for "computer1.mycompany.local".

Hope this helps!

-TM

"jeffuk123" wrote:

> Hello
>
> Setup a Windows 2003 server on a domain with .local namespace and a 18
> character domain name i.e artisticupholstery.local
>
> When users log onto the domain they will only see 'artisticupholst' as the
> domain name. Will this cause any problems?
>
> Everything appears fine elsewhere.
>
> Kind regards,
> Jeff Lee

Many thanks for your reply, I appreciate that.

But will this cause any problems? The reason I ask is that I have seen
articles in the past stating that names longer than 15 characters can cause
some problems, or is this with older servers?

Thanks,
Jeff

"rovert506" wrote:

> By default, Windows truncates the domain name to include only the actual
> domain name when viewed in the log on screen. Thus, "mycompany.local"
> becomes "MYCOMPANY" OR "it.mycompany.local" becomes "IT" or "MYCOMPANY" (both
> options are visible). When you perform pings however, the machine will
> automatically add the entire DNS name. Thus, if you ping computer1, the
> machine will resolve the IP for "computer1.mycompany.local".
>
> Hope this helps!
>
> -TM
>
> "jeffuk123" wrote:
>
> > Hello
> >
> > Setup a Windows 2003 server on a domain with .local namespace and a 18
> > character domain name i.e artisticupholstery.local
> >
> > When users log onto the domain they will only see 'artisticupholst' as the
> > domain name. Will this cause any problems?
> >
> > Everything appears fine elsewhere.
> >
> > Kind regards,
> > Jeff Lee

I would avoid using more than three characters for the TLD (use "loc" instead
of "local"). There are some situations where a TLD longer than 3 causes issues.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not those of my
employer or anyone else associated with me.
-----------------------------------------------------

"jeffuk123" <(E-Mail Removed)> wrote in message
news:A19DD21C-EEB3-4347-BA64-(E-Mail Removed)...
> Many thanks for your reply, I appreciate that.
>
> But will this cause any problems? The reason I ask is that I have seen
> articles in the past stating that names longer than 15 characters can cause
> some problems, or is this with older servers?
>
> Thanks,
> Jeff
>
> "rovert506" wrote:
>
>> By default, Windows truncates the domain name to include only the actual
>> domain name when viewed in the log on screen. Thus, "mycompany.local"
>> becomes "MYCOMPANY" OR "it.mycompany.local" becomes "IT" or "MYCOMPANY" (both
>> options are visible). When you perform pings however, the machine will
>> automatically add the entire DNS name. Thus, if you ping computer1, the
>> machine will resolve the IP for "computer1.mycompany.local".
>>
>> Hope this helps!
>>
>> -TM
>>
>> "jeffuk123" wrote:
>>
>> > Hello
>> >
>> > Setup a Windows 2003 server on a domain with .local namespace and a 18
>> > character domain name i.e artisticupholstery.local
>> >
>> > When users log onto the domain they will only see 'artisticupholst' as the
>> > domain name. Will this cause any problems?
>> >
>> > Everything appears fine elsewhere.
>> >
>> > Kind regards,
>> > Jeff Lee

Names longer than 15 characters only apply to NetBIOS names and were large
issues with versions of Windows prior to 2000/XP. Win2000/XP use DNS as a
name resolution by default and use NetBIOS/WINS if instructed to do so. Host
DNS names, such as computer1, can be considerably longer...up to 64
characters. The entire FQDN (computer.mydomain.local) cannot exceed 255
characters. You can also have subdomains from your main domain that span up
to 127 levels deep. Example: mydomain.local, usa.mydomain.local,
it.usa.mydomain.local, etc.

Hope this helps!

-TM

"jeffuk123" wrote:

> Many thanks for your reply, I appreciate that.
>
> But will this cause any problems? The reason I ask is that I have seen
> articles in the past stating that names longer than 15 characters can cause
> some problems, or is this with older servers?
>
> Thanks,
> Jeff
>
> "rovert506" wrote:
>
> > By default, Windows truncates the domain name to include only the actual
> > domain name when viewed in the log on screen. Thus, "mycompany.local"
> > becomes "MYCOMPANY" OR "it.mycompany.local" becomes "IT" or "MYCOMPANY" (both
> > options are visible). When you perform pings however, the machine will
> > automatically add the entire DNS name. Thus, if you ping computer1, the
> > machine will resolve the IP for "computer1.mycompany.local".
> >
> > Hope this helps!
> >
> > -TM
> >
> > "jeffuk123" wrote:
> >
> > > Hello
> > >
> > > Setup a Windows 2003 server on a domain with .local namespace and a 18
> > > character domain name i.e artisticupholstery.local
> > >
> > > When users log onto the domain they will only see 'artisticupholst' as the
> > > domain name. Will this cause any problems?
> > >
> > > Everything appears fine elsewhere.
> > >
> > > Kind regards,
> > > Jeff Lee

Many thanks guys for all your advice, excellent.

Jeff

"rovert506" wrote:

> Names longer than 15 characters only apply to NetBIOS names and were large
> issues with versions of Windows prior to 2000/XP. Win2000/XP use DNS as a
> name resolution by default and use NetBIOS/WINS if instructed to do so. Host
> DNS names, such as computer1, can be considerably longer...up to 64
> characters. The entire FQDN (computer.mydomain.local) cannot exceed 255
> characters. You can also have subdomains from your main domain that span up
> to 127 levels deep. Example: mydomain.local, usa.mydomain.local,
> it.usa.mydomain.local, etc.
>
> Hope this helps!
>
> -TM
>
> "jeffuk123" wrote:
>
> > Many thanks for your reply, I appreciate that.
> >
> > But will this cause any problems? The reason I ask is that I have seen
> > articles in the past stating that names longer than 15 characters can cause
> > some problems, or is this with older servers?
> >
> > Thanks,
> > Jeff
> >
> > "rovert506" wrote:
> >
> > > By default, Windows truncates the domain name to include only the actual
> > > domain name when viewed in the log on screen. Thus, "mycompany.local"
> > > becomes "MYCOMPANY" OR "it.mycompany.local" becomes "IT" or "MYCOMPANY" (both
> > > options are visible). When you perform pings however, the machine will
> > > automatically add the entire DNS name. Thus, if you ping computer1, the
> > > machine will resolve the IP for "computer1.mycompany.local".
> > >
> > > Hope this helps!
> > >
> > > -TM
> > >
> > > "jeffuk123" wrote:
> > >
> > > > Hello
> > > >
> > > > Setup a Windows 2003 server on a domain with .local namespace and a 18
> > > > character domain name i.e artisticupholstery.local
> > > >
> > > > When users log onto the domain they will only see 'artisticupholst' as the
> > > > domain name. Will this cause any problems?
> > > >
> > > > Everything appears fine elsewhere.
> > > >
> > > > Kind regards,
> > > > Jeff Lee