Mario,
I have a very similar setup, and I had to setup the IP-MASQ machine as a
nameserver. I don't know techincally why this was necessary as on my last
installation I didn't have to. I was having fits until I installed bind,
and it's worked like a charm ever since. I would love an explanation, if
anyone out there knows, why a setup like this seems to break name lookups
from subnet1 subnet2 to the Gateway nameserver.
Ben
[EMAIL PROTECTED]
Hi,
I have set a debian machine as a IP-Masq for 2 subnets:
subnet 1 (most win3.x/95 mach)
|
Gateway-IP-MASQ
nameserver |
subnet 2-(win3.x/95 and Linux(my))
I would like to know:
1. should I set the IP-MASQ machine as nameserver for my 2
subnets?
2. should I put 3 entries in hosts file (one for real IP, one for
subnet1 and other for subnet2)?
3. I'm using SSL, and when I try to connect from my Linux machine
(reserved IP) to the IP-MASQ server, the connect takes a endless time to
be established (30sec). What should I verify to correct this?
thanks,
[]s,
Mario O.de Menezes mailto:[EMAIL PROTECTED]
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
