Intenal hosts cannot reach company website on LAN.

[Guest]

Hi everyone,

I need some help. I have a LAN with a Domain Controller (let's say 192.168.1.100) running DNS behind a Linksys firewall. I have a Web Server which has a differnet IP Address (let's say 192.168.1.50). I have set up my Linksys firewall to forward http traffic to 192.168.1.50. My domain name is, let's say userguide.com. I can reslove the website from any external computer. However, no internal clients on my LAN running behind NAT can gain access. Is there an entry missing?? I set up an alias forthe webserver for both forward and reverse lookup zones but still no luck.

Domain Controller running DNS = 192.168.1.100 or harry.userguide.com
Web Server = 192.168.1.50 or print1.userguide.com

If anyone could help it would be much appreciated.

 

[Ace Fekay [MVP]]

Sounds like the internal domain name and the external domain name are the
same. If so, easy fix. Under your internal zone name, create a www record
and give it the actual external IP address of your webserver.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

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

Hi everyone,

I need some help. I have a LAN with a Domain Controller (let's say

192.168.1.100) running DNS behind a Linksys firewall. I have a Web Server
which has a differnet IP Address (let's say 192.168.1.50). I have set up my
Linksys firewall to forward http traffic to 192.168.1.50. My domain name is,
let's say userguide.com. I can reslove the website from any external
computer. However, no internal clients on my LAN running behind NAT can gain
access. Is there an entry missing?? I set up an alias forthe webserver for
both forward and reverse lookup zones but still no luck.

 

[Jonathan de Boyne Pollard]

MR> I set up an alias forthe webserver for both forward and reverse
MR> lookup zones but still no luck.

What
<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/dns-split-horizon-common-server-names.html>
doesn't (yet) mention is that because many NAT implementations don't
support loopback, from an private IP address to a public IP address
that is mapped back to a second private IP address, you must choose
the private IP address of your content HTTP server and not the
public one in such cases.

 

[Jeff Cochran]

Hi everyone,

I need some help. I have a LAN with a Domain Controller (let's say 192.168.1.100) running DNS behind a Linksys firewall. I have a Web Server which has a differnet IP Address (let's say 192.168.1.50). I have set up my Linksys firewall to forward http traffic to 192.168.1.50. My domain name is, let's say userguide.com. I can reslove the website from any external computer. However, no internal clients on my LAN running behind NAT can gain access. Is there an entry missing?? I set up an alias forthe webserver for both forward and reverse lookup zones but still no luck.

Domain Controller running DNS = 192.168.1.100 or harry.userguide.com
Web Server = 192.168.1.50 or print1.userguide.com

If anyone could help it would be much appreciated.

Add an A record to your internal DNS for the web server's IP.

Jeff