What do you name your AD domain?

[Ashley Heaton]

Thanks in advance for any opinions or help on this.

We are going to be creating a domain soon for our company
and move to it from an old domain that has some issues.
Some of the issues are related to the fact that it was
named the same as a live registered domain that we didn't
own so at times we have name resolution problems.

So now the question.

What are the advantedges and disadvantages (if any) of
having your internal domain named the same as a live
registered domain on the internet? example: company.com;
company.net

What are the advantedges and disadvantafes (if any) of
having your internal domain named so that it isn't
possible to have the internal name registered to be live
in the net. example: company.internal; company.local

I am looking for anything anyone can give. Opinions, hard
facts, documents, anything that would help us make the
right decision.

If there is a "Microsoft Recommended" way for this I would
love to see the documentation on it.

It seems to me that having your internal network setup as
a live registered address possibly invites more problems
than not.

The only problem I can see with not naming it the same as
a registered address would be if your naming convention
ever becomes registerable on the net.

Thanks again,

Ashley Heaton
Nex-Tech
(e-mail address removed)

 

[Richard McCall [MSFT]]

There are more disadvantages to have the domain name that is the same as
your public dns name. Most companies do not want to expose the internal dns
name on the internet. Company.local is a common use of a dns name

 

[Ashley Heaton]

Would you happen to have any specifics besides not wanting
to share your AD DNS names with the world?

I hate to be picky but I have to provide a backed up
argument for whichever way we go.

Thanks,

Ashley Heaton
Nex-tech

-----Original Message-----
There are more disadvantages to have the domain name that is the same as
your public dns name. Most companies do not want to expose the internal dns
name on the internet. Company.local is a common use of a dns name

--
Richard McCall [MSFT]

"This posting is provided "AS IS" with no warranties, and confers no
rights."

Thanks in advance for any opinions or help on this.

We are going to be creating a domain soon for our company
and move to it from an old domain that has some issues.
Some of the issues are related to the fact that it was
named the same as a live registered domain that we didn't
own so at times we have name resolution problems.

So now the question.

What are the advantedges and disadvantages (if any) of
having your internal domain named the same as a live
registered domain on the internet? example: company.com;
company.net

What are the advantedges and disadvantafes (if any) of
having your internal domain named so that it isn't
possible to have the internal name registered to be live
in the net. example: company.internal; company.local

I am looking for anything anyone can give. Opinions, hard
facts, documents, anything that would help us make the
right decision.

If there is a "Microsoft Recommended" way for this I would
love to see the documentation on it.

It seems to me that having your internal network setup as
a live registered address possibly invites more problems
than not.

The only problem I can see with not naming it the same as
a registered address would be if your naming convention
ever becomes registerable on the net.

Thanks again,

Ashley Heaton
Nex-Tech
(e-mail address removed)

.

 

[Scott Harding - MS MVP]

Check these "Official MS Docs"

http://support.microsoft.com/default.aspx?scid=kb;en-us;254680

http://support.microsoft.com/default.aspx?scid=kb;en-us;285983


--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

Would you happen to have any specifics besides not wanting
to share your AD DNS names with the world?

I hate to be picky but I have to provide a backed up
argument for whichever way we go.

Thanks,

Ashley Heaton
Nex-tech

-----Original Message-----
There are more disadvantages to have the domain name that is the same as
your public dns name. Most companies do not want to expose the internal dns
name on the internet. Company.local is a common use of a dns name

--
Richard McCall [MSFT]

"This posting is provided "AS IS" with no warranties, and confers no
rights."

Thanks in advance for any opinions or help on this.

We are going to be creating a domain soon for our company
and move to it from an old domain that has some issues.
Some of the issues are related to the fact that it was
named the same as a live registered domain that we didn't
own so at times we have name resolution problems.

So now the question.

What are the advantedges and disadvantages (if any) of
having your internal domain named the same as a live
registered domain on the internet? example: company.com;
company.net

What are the advantedges and disadvantafes (if any) of
having your internal domain named so that it isn't
possible to have the internal name registered to be live
in the net. example: company.internal; company.local

I am looking for anything anyone can give. Opinions, hard
facts, documents, anything that would help us make the
right decision.

If there is a "Microsoft Recommended" way for this I would
love to see the documentation on it.

It seems to me that having your internal network setup as
a live registered address possibly invites more problems
than not.

The only problem I can see with not naming it the same as
a registered address would be if your naming convention
ever becomes registerable on the net.

Thanks again,

Ashley Heaton
Nex-Tech
(e-mail address removed)

.

 

[Ashley Heaton]

Thank you very much for your help Gentlemen.

I appreciate it very much, I think I have found exactly
what I need.

Thanks again,

Ashley Heaton
Nex-Tech