Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

resolving IIS website internally 1

Status
Not open for further replies.

mekon

Technical User
Feb 13, 2002
21
GB
hi all

I think this is more of a DNS issue, than IIS..

We have a client that has two servers, DC and WEB

DC is the PDC/DNS/WINS/AD server, running Windows Server 2003. the AD domain name is DOMAIN.LOCAL

WEB is the webserver, running Windows Server 2003, and IIS V6.0 that contains the company website

the domain/hosting company forwards the domain to the company's firewall, that then redirects port 80 to the internal IP of the webserver. all works fine

PCs within the company network use the internal DNS server, and the firewall as the gateway

the question I have is that with the current setup, how can internal requests for be directed to the webserver?

An entry can be put in the HOSTS file, linking the web address to the internal web server IP, or the internal IP can be used directly in the browser etc - but is the only other solution to change the AD domain name from DOMAIN.LOCAL to COMPANY.COM?

thanks
 
Assuimg your are not hosting your own zone then you just need to create a new "Forward Lookup Zone" on your DNS server for "company.com" and then create an "A" record for "www" that points to the INTERNAL address of the webserver.

The Client PCs should be configured that their DNS is the "DC" server, not the ISPs DNS server.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top