Reverse resolution from a private subnet to another privatesubnet

Brett Simpson Simpsonb at hillsboroughcounty.org
Thu Aug 14 20:38:14 UTC 2003


Figured it out. It was a nat problem on Firewall A.

>>> "Brett Simpson" <Simpsonb at hillsboroughcounty.org> 08/14/03 09:40AM >>>
I think I'm having a reverse resolution problem with a workstation that =
=3D
resides on a private subnet that tries to connect to a server in another =
=3D
private subnet.=3D20

Here is the topology:

workstation 192.168.0.211
      |
firewall A 192.168.0.1(gateway) - 207.156.7.121
      |
firewall B 207.156.7.1 (gateway) 172.16.21.103
      |
cisco switch/router 172.16.3.119 (gateway)
      |
cisco switch/router 192.168.100.60

All of the systems can access my DNS servers, both DNS servers (master and =
=3D
slave) have forward and reverse entries for the 192.168.0.211 and =3D
192.168.100.60. The 192.168.0.x is a Masqeraded subnet behind Firewall A. =
=3D
The 207.x, 172.x, and 192.168.100.x subnets are accessable by all =3D
systems.=3D20

The problem is when I try to connect to a web service on 192.168.100.60 =
=3D
from 192.168.0.211 it takes 30 seconds to get the login. But when I try =
=3D
from Firewall A, any machine in the 207.x, 172.x, or 192.168.100.x subnet =
=3D
it responds in less than 5 seconds.

Is this a problem were the web server 192.168.100.60 cannot directly =3D
access 192.168.0.211 since 192.168.0.x is a hidden subnet?






More information about the bind-users mailing list