DNS Configuration Question.

We have recently moved our internal web site to an external host. Computers
on other external networks can access out new website just fine.

However, our server and client machines canâ??t navigate to the new site. Can
anyone give me some pointers on what to add to the forward and reverse lookup
zones within DNS to allow our internal machines the ability to connect to our
new externally hosted website?

Thanks
Ron

Lanwench
Sat Apr 08 15:43:29 PDT 2006



In news:5E715C75-14A1-45BB-BBC8-080B0792DB43@microsoft.com,
Ron C. <Ron C.@discussions.microsoft.com> typed:
> We have recently moved our internal web site to an external host.
> Computers on other external networks can access out new website just
> fine.
>
> However, our server and client machines can't navigate to the new
> site. Can anyone give me some pointers on what to add to the forward
> and reverse lookup zones within DNS to allow our internal machines
> the ability to connect to our new externally hosted website?
>
> Thanks
> Ron

If you named your AD domain name mycompany.com, and that's your real/public
domain name, your internal DNS server naturally presumes that it's
responsible for everything.mycompany.com and will

This is one of the reasons that you need to be careful when setting up
Active Directory....there's nothing innately *wrong* with this setup, but if
you aren't careful and don't think about the possible permutations, you can
find yourself in this situation.

That said, you can either set up a host in your forward-lookup zone, called
www, and specify your public IP therein. If you don't have a static IP for
your public website/hosting account, or don't want to have a lot of fuss and
bother when/if that IP changes there are other ways, but generally speaking,
the above should work.

RonC
Sat Apr 08 18:20:01 PDT 2006

Thanks for the reply. I added a www host record in the dns forward lookup
zone. The record points to a static ip provided by the web hosting provider.
Thanks again.

"Lanwench [MVP - Exchange]" wrote:

>
>
> In news:5E715C75-14A1-45BB-BBC8-080B0792DB43@microsoft.com,
> Ron C. <Ron C.@discussions.microsoft.com> typed:
> > We have recently moved our internal web site to an external host.
> > Computers on other external networks can access out new website just
> > fine.
> >
> > However, our server and client machines can't navigate to the new
> > site. Can anyone give me some pointers on what to add to the forward
> > and reverse lookup zones within DNS to allow our internal machines
> > the ability to connect to our new externally hosted website?
> >
> > Thanks
> > Ron
>
> If you named your AD domain name mycompany.com, and that's your real/public
> domain name, your internal DNS server naturally presumes that it's
> responsible for everything.mycompany.com and will
>
> This is one of the reasons that you need to be careful when setting up
> Active Directory....there's nothing innately *wrong* with this setup, but if
> you aren't careful and don't think about the possible permutations, you can
> find yourself in this situation.
>
> That said, you can either set up a host in your forward-lookup zone, called
> www, and specify your public IP therein. If you don't have a static IP for
> your public website/hosting account, or don't want to have a lot of fuss and
> bother when/if that IP changes there are other ways, but generally speaking,
> the above should work.
>
>
>
>

Lanwench
Sat Apr 08 21:52:36 PDT 2006



In news:B016508F-7AAE-4625-B003-B089EB4D5A92@microsoft.com,
Ron C. <RonC@discussions.microsoft.com> typed:
> Thanks for the reply. I added a www host record in the dns forward
> lookup zone. The record points to a static ip provided by the web
> hosting provider. Thanks again.

You're welcome; glad it worked out.

>
> "Lanwench [MVP - Exchange]" wrote:
>
>>
>>
>> In news:5E715C75-14A1-45BB-BBC8-080B0792DB43@microsoft.com,
>> Ron C. <Ron C.@discussions.microsoft.com> typed:
>>> We have recently moved our internal web site to an external host.
>>> Computers on other external networks can access out new website just
>>> fine.
>>>
>>> However, our server and client machines can't navigate to the new
>>> site. Can anyone give me some pointers on what to add to the forward
>>> and reverse lookup zones within DNS to allow our internal machines
>>> the ability to connect to our new externally hosted website?
>>>
>>> Thanks
>>> Ron
>>
>> If you named your AD domain name mycompany.com, and that's your
>> real/public domain name, your internal DNS server naturally presumes
>> that it's responsible for everything.mycompany.com and will
>>
>> This is one of the reasons that you need to be careful when setting
>> up Active Directory....there's nothing innately *wrong* with this
>> setup, but if you aren't careful and don't think about the possible
>> permutations, you can find yourself in this situation.
>>
>> That said, you can either set up a host in your forward-lookup zone,
>> called www, and specify your public IP therein. If you don't have a
>> static IP for your public website/hosting account, or don't want to
>> have a lot of fuss and bother when/if that IP changes there are
>> other ways, but generally speaking, the above should work.