All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shaun T. Erickson" <ste@smxy.org>
To: Jason Opperisano <Jopperisano@alphanumeric.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Need to replace a SonicWall firewall with an iptables firewall.
Date: Tue, 31 Aug 2004 09:47:36 -0400	[thread overview]
Message-ID: <41348178.4080701@smxy.org> (raw)
In-Reply-To: <D5C9032B2B09C64EA2409D6214E91AC905130B@asimail2.alphanumeric.com>

>>I need internal hosts, and external hosts, to be able to connect to the
>>DMZ servers by their public DNS names. Connecting to
>>http://www.somedomain.com from either the inside or the outside, should
>>get you to the server in the DMZ. For testing purposes, we need to
>>access everything the same way as our customers.
> 
> 
> this statement implies you would want split-dns...
> 
> 
>>Not knowing what split-dns was, I googled it. If I understand it
>>correctly it seems that this is only needed when you use a single,
>>common domain for both internal and external systems. All our external
>>systems (both between the firewall and the router, and in the DMZ) are
>>in "domain.com" and all our internal systems are in "sub.domain.com", so
>>we don't need split-dns, right?
> 
> 
> whereas this statement implies you don't want split-dns.

It's not a matter of what I want or don't want - I inherited this mess 
from someone else, recently, and I'm slowly working my way through all 
my systems, learning how they are working (or not). We don't currently 
have split-dns (see my reply to the off-topic portion of this thread). 
Systems in the DMZ currently use real IP addresses, and can be accessed 
by their name in our external domain, from either the Internet, or from 
our internal domain (a sub-domain of our external domain). I'm trying to 
replicate this with an iptables firewall, without having to eliminate 
our internal domain and completely re-doing our internal and external 
dns in a split-dns fashion, just to get the firewall to work. Should I 
go to split-dns? From what I've read, and been told here, it would seem 
an excellent thing to do, but it's not something I can do overnight.

I mentioned in another email, that I could probably get two subnets from 
my ISP - one for my external network and one for my DMZ. Would this 
solve the problem until I can migrate to a split dns and one-to-one 
NAT'ing of the DMZ systems?

	-ste


  reply	other threads:[~2004-08-31 13:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-30 22:25 Need to replace a SonicWall firewall with an iptables firewall Jason Opperisano
2004-08-31 13:47 ` Shaun T. Erickson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-31 14:11 Jason Opperisano
2004-08-30 22:23 Daniel Chemko
2004-08-31  0:02 ` Nick Drage
2004-08-30 20:45 Jason Opperisano
2004-08-30 20:41 Jason Opperisano
2004-08-30 21:11 ` Shaun T. Erickson
2004-08-30 19:30 Jason Opperisano
2004-08-30 20:23 ` Shaun T. Erickson
2004-08-30 16:01 Shaun T. Erickson
2004-08-30 18:41 ` Shaun T. Erickson

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=41348178.4080701@smxy.org \
    --to=ste@smxy.org \
    --cc=Jopperisano@alphanumeric.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.