Very Computer

My intranet DNS resolves www hostnames to the extranet IP of the reverse
proxy/firewall.  So when I use the URL http://www.domain.com/resource from
within the interanet, DNS actually tries to resolve the reverse
proxy/firewall machine's IP in order to, or what I hope to be, a resolution
of the forwarded http port on the reverse proxy/firewall.

I have no problem accessing the same URL resources from the Internet (from
extranet, using extranet hostname/IP to intranet resource is OK).
Also, I have no problem accessing the resource using the intranet IP address
in the URL (from intranet, using intranet hostname/IP to intranet resource
is OK).
But I cannot access the resource from the intranet, using the URL which
works perfectly from the extranet (from intranet, using extranet hostname/IP
to interanet is a problem).

Is this a routing problem or a firewall port problem?

Any help would be greatly appreciated.

Thanks in advance.

I guess the problem is your DNS server. If you've established a zone named
'domain.com' it tries to resolve *ALL* adresses for that certain zone and will
not ask
the external DNS for the correct IP address. So all you have to do is add the
relevant
'A record' for the www server in your zone file. I.e.

// file  /var/named/domain.com
www        A    111.222.333.444

Then you should be able to get in contact with your web server from within your
intranet.

Keivan Khalichi schrieb:

Quote:> I'm running a firewall on Mandrake Linux 6.1 and using IPMASQADM for reverse
> proxy to forward http requests from the Internet to the intranet and visa
> versa.  Both IPMasqADM and IPMasquerading work great.  I have a web page on
> a web server which is on my intranet that is accessible from the Internet
> using the reverse proxy/firewall.  When I try to access this web page from
> the intranet, using the IP address of the reverse proxy/firewall machine
> which is normally used when one is attempting to access the page from
> Internet, the browser is unable to resolve the URLs.

> My intranet DNS resolves www hostnames to the extranet IP of the reverse
> proxy/firewall.  So when I use the URL http://www.domain.com/resource from
> within the interanet, DNS actually tries to resolve the reverse
> proxy/firewall machine's IP in order to, or what I hope to be, a resolution
> of the forwarded http port on the reverse proxy/firewall.

> I have no problem accessing the same URL resources from the Internet (from
> extranet, using extranet hostname/IP to intranet resource is OK).
> Also, I have no problem accessing the resource using the intranet IP address
> in the URL (from intranet, using intranet hostname/IP to intranet resource
> is OK).
> But I cannot access the resource from the intranet, using the URL which
> works perfectly from the extranet (from intranet, using extranet hostname/IP
> to interanet is a problem).

> Is this a routing problem or a firewall port problem?

> Any help would be greatly appreciated.

> Thanks in advance.