From: Chris Brenton <cbrenton@chrisbrenton.org>
To: Martin Leduc <marled3@hotmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Problem behind my DMZ
Date: Wed, 07 Jan 2004 21:27:42 -0500 [thread overview]
Message-ID: <1073528862.2049.825.camel@grendel> (raw)
In-Reply-To: <001b01c3d57d$15123950$0296a8c0@martin>
Greetings!
On Wed, 2004-01-07 at 19:19, Martin Leduc wrote:
>
> One of my server is DNS. My trouble is if I tried to send Email FROM
> one of this third server, my DNS return to sender server the public IP
> and my Email as send to my firewall, not my internal Server.
Common problem. You have two potential solutions:
1) Use public IPs on your DMZ/service network. This will also give you a
performance boost as you will drop the NAT overhead. You don't mention
how many legal IPs you have, but if you have enough address space to
carve off a /29 or /28 for your DMZ, this would be your best bet.
2) Use split DNS. Setup another name server that is accessible only from
internal systems and populate it with your private addresses.
HTH,
C
next prev parent reply other threads:[~2004-01-08 2:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 0:19 Problem behind my DMZ Martin Leduc
2004-01-08 2:27 ` Chris Brenton [this message]
2004-01-08 16:31 ` Michael Gale
-- strict thread matches above, loose matches on Subject: below --
2004-01-08 15:53 Martin Leduc
2004-01-08 16:16 ` Antony Stone
2004-01-08 18:10 ` Ramin Dousti
2004-01-08 17:17 ` Antony Stone
2004-01-08 19:18 ` Ramin Dousti
2004-01-08 17:12 Martin Leduc
2004-01-08 17:22 ` Antony Stone
2004-01-08 17:46 Martin Leduc
2004-01-08 17:53 ` Antony Stone
2004-01-09 2:19 Martin Leduc
2004-01-09 4:14 ` Ramin Dousti
2004-01-09 9:54 Martin Leduc
2004-01-09 10:57 ` Antony Stone
2004-01-09 15:26 ` Ramin Dousti
2004-01-10 12:55 Martin Leduc
2004-01-10 13:26 Martin Leduc
2004-01-12 12:08 Martin Leduc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1073528862.2049.825.camel@grendel \
--to=cbrenton@chrisbrenton.org \
--cc=marled3@hotmail.com \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox