External and internal domains and DNS Server

Hi,

I have the company.com Internet domain which serves the company's public
Internet website at www.company.com. The authoritative name server for this
domain is somewhere in the Internet.

Now I installed a new domain controller on Windows Server 2008 for a new
internal domain which I called company.com as well. I guess it wasn't a wise
decision because if I type www.company.com on a machine that belongs to the
internal domain, the address can't be resolved.

It's understandable because the domain controller has the DNS Server
installed which knows nothing about the external company.com domain.

Is it possible to configure the internal DNS server to properly handle both
the internal and external domain names? For example, I want all local DNS
queries which can't be resolved locally (like www.company.com) to be
forwarded to the external DNS server.

Thanks,
John

Jabez
Mon Mar 24 19:49:13 PDT 2008

Hi John,

Yes in fact, you should create an internal DNS only for your internal
computers to resolve the hostnames. And you dont want to have your local DNS
queries resolved by your external DNS server - you can have two copies -
external and internal copies of DNS.

--
Jabez Gan
Microsoft MVP: Windows Server
http://www.msblog.org


"muriwai" <muriwai@nospam.nospam> wrote in message
news:OZGx5IhjIHA.2396@TK2MSFTNGP05.phx.gbl...
> Hi,
>
> I have the company.com Internet domain which serves the company's public
> Internet website at www.company.com. The authoritative name server for
> this domain is somewhere in the Internet.
>
> Now I installed a new domain controller on Windows Server 2008 for a new
> internal domain which I called company.com as well. I guess it wasn't a
> wise decision because if I type www.company.com on a machine that belongs
> to the internal domain, the address can't be resolved.
>
> It's understandable because the domain controller has the DNS Server
> installed which knows nothing about the external company.com domain.
>
> Is it possible to configure the internal DNS server to properly handle
> both the internal and external domain names? For example, I want all local
> DNS queries which can't be resolved locally (like www.company.com) to be
> forwarded to the external DNS server.
>
> Thanks,
> John
>

cristalink
Tue Mar 25 19:03:02 PDT 2008

I ended up renaming the domain with RENDOM.

Thanks


"Jabez Gan [MVP]" <mingteikg@blizNOSPAMhosting.com> wrote in message
news:3FCB474F-4DF0-4C0C-B754-4BC7CCFC83C3@microsoft.com...
> Hi John,
>
> Yes in fact, you should create an internal DNS only for your internal
> computers to resolve the hostnames. And you dont want to have your local
> DNS queries resolved by your external DNS server - you can have two
> copies - external and internal copies of DNS.
>
> --
> Jabez Gan
> Microsoft MVP: Windows Server
> http://www.msblog.org
>
>
> "muriwai" <muriwai@nospam.nospam> wrote in message
> news:OZGx5IhjIHA.2396@TK2MSFTNGP05.phx.gbl...
>> Hi,
>>
>> I have the company.com Internet domain which serves the company's public
>> Internet website at www.company.com. The authoritative name server for
>> this domain is somewhere in the Internet.
>>
>> Now I installed a new domain controller on Windows Server 2008 for a new
>> internal domain which I called company.com as well. I guess it wasn't a
>> wise decision because if I type www.company.com on a machine that belongs
>> to the internal domain, the address can't be resolved.
>>
>> It's understandable because the domain controller has the DNS Server
>> installed which knows nothing about the external company.com domain.
>>
>> Is it possible to configure the internal DNS server to properly handle
>> both the internal and external domain names? For example, I want all
>> local DNS queries which can't be resolved locally (like www.company.com)
>> to be forwarded to the external DNS server.
>>
>> Thanks,
>> John
>>
>