forest domain name

Hi all,

Today, I just had a big discussion with AD design team:
they propose that our internal domain name should be xy.net and our
compnay's external domain name is xy.com. I just wonder why use xy.net for
internal domain name and we should use xy.local for our internal domain name
to seperate internal and external domain even though xy.net is not registered.

Can anyone help me out?

Thank you.

Hello ed,

The internal/external domain name shouldn't be equal as this require additional
configuration for DNS. On example is a webpage that is accessible from the
internet with www.domain.com, internal without additonal configuration you
can't open it that way.

If you don't have an external domain name yet, it doesn't matter how you
name it. But i assume your AD design team is thinking about the future and
their recommendation is quite correct, to better separate the external and
internal domain name. The TLD that you use internal shouldn't be able to
be registered in the public. This reduces some configuration and problems
like the webpage example.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hi all,
>
> Today, I just had a big discussion with AD design team:
> they propose that our internal domain name should be xy.net and our
> compnay's external domain name is xy.com. I just wonder why use
> xy.net for
> internal domain name and we should use xy.local for our internal
> domain name
> to seperate internal and external domain even though xy.net is not
> registered.
> Can anyone help me out?
>
> Thank you.
>

Meinolf,

Thank you for your help.

I mean why the design team recommend to use xy.NET for our INTERNAL domain
name and why do we just use xy.LOCAL for our internal domain and totally
seperate internal and external DNS name as you mentioned too. Here is my
reasoning that xy.net can be registered in Public DNS though nobody registers
xy.NET yet. (We already registered xy.com for our external domain name and
this is right. ) I am talking about why using xy.net for INTERNAL domain
name?

thank you.




"Meinolf Weber [MVP-DS]" wrote:

> Hello ed,
>
> The internal/external domain name shouldn't be equal as this require additional
> configuration for DNS. On example is a webpage that is accessible from the
> internet with www.domain.com, internal without additonal configuration you
> can't open it that way.
>
> If you don't have an external domain name yet, it doesn't matter how you
> name it. But i assume your AD design team is thinking about the future and
> their recommendation is quite correct, to better separate the external and
> internal domain name. The TLD that you use internal shouldn't be able to
> be registered in the public. This reduces some configuration and problems
> like the webpage example.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > Hi all,
> >
> > Today, I just had a big discussion with AD design team:
> > they propose that our internal domain name should be xy.net and our
> > compnay's external domain name is xy.com. I just wonder why use
> > xy.net for
> > internal domain name and we should use xy.local for our internal
> > domain name
> > to seperate internal and external domain even though xy.net is not
> > registered.
> > Can anyone help me out?
> >
> > Thank you.
> >
>
>
> .
>

Hello ed,

It is not important which one you use for the internal domain name. If it
is registered it will still have a different ip address and no DNS registrar
should use your public ip address for that name, so even if someone use the
xy.net all requests for that domain name will be linked to the other companies
ip address.

Personal i would not use a TLD that is able to be registered in the public
at the moment. But as long as the name is registered with another companies
ip address, it shouldn't matter for your internal name.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Meinolf,
>
> Thank you for your help.
>
> I mean why the design team recommend to use xy.NET for our INTERNAL
> domain name and why do we just use xy.LOCAL for our internal domain
> and totally seperate internal and external DNS name as you mentioned
> too. Here is my reasoning that xy.net can be registered in Public DNS
> though nobody registers xy.NET yet. (We already registered xy.com for
> our external domain name and this is right. ) I am talking about why
> using xy.net for INTERNAL domain name?
>
> thank you.
>
> "Meinolf Weber [MVP-DS]" wrote:
>
>> Hello ed,
>>
>> The internal/external domain name shouldn't be equal as this require
>> additional configuration for DNS. On example is a webpage that is
>> accessible from the internet with www.domain.com, internal without
>> additonal configuration you can't open it that way.
>>
>> If you don't have an external domain name yet, it doesn't matter how
>> you name it. But i assume your AD design team is thinking about the
>> future and their recommendation is quite correct, to better separate
>> the external and internal domain name. The TLD that you use internal
>> shouldn't be able to be registered in the public. This reduces some
>> configuration and problems like the webpage example.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Hi all,
>>>
>>> Today, I just had a big discussion with AD design team:
>>> they propose that our internal domain name should be xy.net and our
>>> compnay's external domain name is xy.com. I just wonder why use
>>> xy.net for
>>> internal domain name and we should use xy.local for our internal
>>> domain name
>>> to seperate internal and external domain even though xy.net is not
>>> registered.
>>> Can anyone help me out?
>>> Thank you.
>>>
>> .
>>

On Sat, 12 Jun 2010 09:14:35 -0700, ed <>
wrote:

>Meinolf,
>
>Thank you for your help.
>
>I mean why the design team recommend to use xy.NET for our INTERNAL domain
>name and why do we just use xy.LOCAL for our internal domain and totally
>seperate internal and external DNS name as you mentioned too. Here is my
>reasoning that xy.net can be registered in Public DNS though nobody registers
>xy.NET yet. (We already registered xy.com for our external domain name and
>this is right. ) I am talking about why using xy.net for INTERNAL domain
>name?
>
>thank you.
>
>
>

Hello, Ed,

The domain name choice could have been made either by a personal
choice because the team was comfortable with it, or by some other
choice. Hard to tell. Either way, as Meinolf said, whichever you
choose there are pros and cons with either name.

I created a blog on this, link posted below. I hope you find it
informative.

What's in an Active Directory DNS Name? Choosing a domain name.
http://msmvps.com/blogs/acefekay/arc...main-name.aspx

Ace

This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.