Can't access local website

[garyd]

I have a Windows 2000 DC running DNS. As Microsoft
suggests, it is configured with a domain name that matches
the domain name for the website. Since the server is
configured with DNS and points to itself, then forwards
any other requests to the ISP (where the website also
resides) everything works fine except that the client
workstations cannot access the website because the server
will not forward these requests to the ISP. I suspect
that it assumes that it is resolved when it reaches the
server.

If I configure the client workstations using the ISP's DNS
server addresses they will be able to access the website
but other local requests take far too long be resolved (or
time-out) at the ISP.

How do I need to configure DNS on the server or
workstations so that the workstations will have access to
their own website?

Thanks,

Gary Drost

 

[Kevin D. Goodknecht Sr. [MVP]]

In garyd <[email protected]>
posted their concerrns,
Then Kevin D4Dad added his reply at the bottom.

I have a Windows 2000 DC running DNS. As Microsoft
suggests, it is configured with a domain name that matches
the domain name for the website. Since the server is
configured with DNS and points to itself, then forwards
any other requests to the ISP (where the website also
resides) everything works fine except that the client
workstations cannot access the website because the server
will not forward these requests to the ISP. I suspect
that it assumes that it is resolved when it reaches the
server.

If I configure the client workstations using the ISP's DNS
server addresses they will be able to access the website
but other local requests take far too long be resolved (or
time-out) at the ISP.

How do I need to configure DNS on the server or
workstations so that the workstations will have access to
their own website?

Thanks,

Gary Drost

In your local forward lookup zone for your domain add a new host named www
and point it to the public address of your external web site.

 

[Ace Fekay [MVP]]

In

I have a Windows 2000 DC running DNS. As Microsoft
suggests, it is configured with a domain name that matches
the domain name for the website. Since the server is
configured with DNS and points to itself, then forwards
any other requests to the ISP (where the website also
resides) everything works fine except that the client
workstations cannot access the website because the server
will not forward these requests to the ISP. I suspect
that it assumes that it is resolved when it reaches the
server.

If I configure the client workstations using the ISP's DNS
server addresses they will be able to access the website
but other local requests take far too long be resolved (or
time-out) at the ISP.

How do I need to configure DNS on the server or
workstations so that the workstations will have access to
their own website?

Thanks,

Gary Drost

Follow Kevin's suggestion. Also, just keep in mind to not use your ISP's DNS
server in your internal machine's properties or errors can result.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[garyd]

I added the new HOST record and it appears to work
perfectly. Thanks for the fix - this one has been a
nagging back burner issue for some time, I was never able
to find a solution in the KB.

Again thanks,

Gary