After DC/AD/DNS was set up company's main URL can not be hit internally

[Syano]

**********
Situation:
**********
Client Machines:
10 WinXP client machines (primary DNS server of these
machines is 10.0.0.1)

Server:
1 Win2000 Server acting as the DC and DNS server for its
domain. (IP of server is 10.0.0.1) (Windows Domain Name
is domain.com)

The DNS server has the "fowarders" tab turned on, and the
IPs it forwards to are the primary and secondary DNS
address of the ISP's name servers lets say these
addresses are 67.67.67.68 and 69)

Website hosted by ISP:
WebSite hosted by a 3rd party ISP (website's URL is
www.domain.com) (lets say the IP address of the website
is 67.67.67.67)

********
Problem:
********
Everything works fine, accept when the client machines
open their web browsers and go to the URL www.domain.com
the page can not be found. Yet all other internet URLs
come up fine.

**********
What I did:
**********
As a temporary workaround I added a static entry in each
of the clients HOST file specifying www.domain.com =
67.67.67.67. And it worked. The URL www.domain.com comes
up fine now.

*********
Question:
*********

What is a better way to handle this? My solution has an
assortment of potential problems that I want to avoid.

Thanks for listening,

S

 

[Herb Martin]

What I did:

As a temporary workaround I added a static entry in each
of the clients HOST file specifying www.domain.com =
67.67.67.67. And it worked. The URL www.domain.com comes
up fine now.

Instead, add all the EXTERNAL records MANUALLY to the internal
version of the zone.

*********
What is a better way to handle this? My solution has an
assortment of potential problems that I want to avoid.

Do it in DNS (see above) instead. The only disadvantage is that you must
add/change all external records at both the ISP AND the INTERNAL DNS
servers. It's called "Shadow DNS".

 

[Guest]

Thanks for you response Herb, however it gave me nothing
to work with.

S

 

[Herb Martin]

Which part did you fail to understand? Go back and reply to my
message (inline) and ask a question.

 

[Paul McGuire]

In DNS on your server add a host with the name of "www" and then point it to
the IP of your webpage that is hosted externally. if you have ftp or mail
hosted externally then also add those hosts in DNS. With all of your
clients pointing to your DNS server and forwarders setup correctly then
everything should work

 

[Guest]

I had a similar situation.

Actually, I had previously set up MS DNS servers before the AD migration. I
found out later they couldn't be upgraded to AD-integrated zones, so I'm
running DNS on a small scale on the DC with forwarding to our internal DNS
servers turned on.

Instead of dinking with Host tables, I created an Alias for 'www' on the AD
DNS server so the internal address could be resolved.

Seems to work,

~K

********


Everything works fine, accept when the client machines

open their web browsers and go to the URL www.domain.com

 

[Herb Martin]

Actually, I had previously set up MS DNS servers before the AD migration.
I

found out later they couldn't be upgraded to AD-integrated zones, so I'm

That's not the case -- an MS DNS server on Win2000 or Win2003 that is a DC
can be freely changed from an ordinary DNS server to AD and back.

There may be issues of replication if you don't think this through and make
adjustments. But such adjustments are fairly trivial and there is no
technical
reason that prevents the conversion.