Re: port redirection with natd and ipfw
- From: "Nilton Volpato" <nilton.volpato@xxxxxxxxx>
- Date: Fri, 24 Nov 2006 02:16:25 -0300
[Fratiman Vladut]
This is because u try to access an ip that have same ip like your
gateway, but from internal lan, so packets are sends to gateway but
cannot be redirected back to the http server according with redirect
rules.
To resolve this situation, configure a simple dns server on your
gateway, and make a zone with your domain pointed to the internal ip.
Then configure the computers clients to ask your dns server. This is
easily done via dhcp.
Your dns server need to be configured to forward request's for unknow
domains to the autoritarive public dns servers.
--
Best regards,
Fratiman
[Russell Wood]
I had a similar setup once and used Split DNS with BIND. So, if you
requested example.com on 192.168.0.0/24 then you'd get the internal IP,
otherwise you got the external IP.
Regards,
Russell Wood
Thanks guys,
But Split DNS does not work in my case. Because I have different
services on different machines, and the dns will map one name (and all
ports associated to it) to one machine.
Is there any solution that will work without using split dns?
Thanks,
-- Nilton
_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"
- References:
- RE: port redirection with natd and ipfw
- From: Wood, Russell
- RE: port redirection with natd and ipfw
- Prev by Date: Re: Continued Crashing of Mozilla FF
- Next by Date: Re: > Subject: Re: Ezmlm Port Okay Or Junk?
- Previous by thread: RE: port redirection with natd and ipfw
- Next by thread: Modifying gcc34 makefile to compile with java
- Index(es):
Relevant Pages
|