Posts: 111
Joined: 5.Oct.2001
From: San Francisco, CA 94102
Status: offline
Based on reading the Book of the Month advertised on this site. A nice book I think. I've set up DNS on the ISA machine with a forward and reverse lookup zone for datasculpting.com pointing to the public IP address. Then I add a Host record for www pointing to the internal IP of the web server (seperate machine inside the proxy). When I do a nslookup for www.datasculpting.com, it returns the 10. number and I'm unable to resolve and see the web servers pages. Any help. I'm a software designer for the most part and much of this is outside my area of expertise. Any help on setting up DNS for web publishing of an internal web server would be of great help to me.
Based on my experience, if the Web site is not located on ISA Server itself and it is using port 80, you should be able to view the Web page from an internal client when your DNS resolves your Web site name to an internal IP.
However, if your Web server is located on the ISA Server itself, you must have followed Tom's advise and redirect the external IP address listening to port 80 to an internal IP using another port. In that configuration, based on my experience, the DNS for your web site's name should return the external IP instead of the internal. I think this is because IIS on ISA is not listeing to port 80. Therefore, an internal client will not find the Web site using the internal address.
Posts: 111
Joined: 5.Oct.2001
From: San Francisco, CA 94102
Status: offline
Sorry. I should have been more specific. The web server is on another machine (other than the ISA server) and is connected to the ISA server via a hub and is set up with one nic card set to a non class c ip address 10.3... I can browse the site www.datasculpting.com (66.123.210.66) which is redirected through ISA to the 10.3.. number but I can't view the site from outside my LAN. Any suggestions? The zone is datasculpting.com 66.123.210.66 with a host record for www set to 10.3...
Posts: 18
Joined: 6.Mar.2001
From: Renton, WA USA
Status: offline
People on the internet is not going to be able to see 10.3... You need to set the www host to 66.123.210.66. In your destination set, make sure the FQDN is www.datasculpting.com and then set the web publishing rule to use that destination set and set the action to forward requests to 10.3...
Posts: 111
Joined: 5.Oct.2001
From: San Francisco, CA 94102
Status: offline
So in Tom's book on page 616 where he states "You will need to inlcude a Host (A) entry for the internal Web server you wish to publish", does this mean that I set the www record to the 66.... number in the 66... domain.com zone or to the 10.... number in the 66.... domain.com zone? Where exactly, if anywhere, do I make an entry for 10.... number?
Posts: 111
Joined: 5.Oct.2001
From: San Francisco, CA 94102
Status: offline
I set the zone and www host record to 66.123.210.66. The destination set is pointing to destination www.datasculpting.com. Do I have to put the http:// before this? The web publishing rule routes the request to the 10.3 number. I get an http 403 error when I try http://66.123.210.66 and nothing when I try http://www.datasculpting.com. Any ideas?
Thanks.
quote:Originally posted by GAMacky: People on the internet is not going to be able to see 10.3... You need to set the www host to 66.123.210.66. In your destination set, make sure the FQDN is www.datasculpting.com and then set the web publishing rule to use that destination set and set the action to forward requests to 10.3...