All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Drage <nickd@funkyjesus.org>
To: netfilter@lists.samba.org
Subject: Re: iptables and DNS
Date: Tue, 4 Jun 2002 18:52:23 +0100	[thread overview]
Message-ID: <20020604185223.T27307@funkyjesus.org> (raw)
In-Reply-To: <scfc997d.097@pzsj-office.pzs.com>; from bugie@pzs.com on Tue, Jun 04, 2002 at 10:41:58AM -0700

On Tue, Jun 04, 2002 at 10:41:58AM -0700, Brian Ugie wrote:
> Below  is the hosts portion of nsswitch.conf.  The actual hosts file is
> below that. I have also included the simple config that I am using for
> iptables. I have seen the -n option but it is not relevant for appending,
> inserting or replacing. It only applies to listing (output)

Er, unless I'm missing something, you're using hostnames in your IPTables
rules, and then complaining that IPTables is resolving those hostnames?

Excuse me if this sounds obvious, but why not use IP addresses in the rule
specifications.  If you're worried about having to alter all the relevant
rules if an IP address changes then just assign it to a variable...

#!/bin/sh -x

WEBSERVER="10.10.10.13"

iptables -A INPUT -p tcp -d $WEBSERVER --dport 80 -j ACCEPT
iptables -A INPUT -p tcp -d $WEBSERVER -j REJECT --reject-with tcp-reset

etc. 

<snip>

-- 
FunkyJesus System Administration Team



  reply	other threads:[~2002-06-04 17:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 17:41 iptables and DNS Brian Ugie
2002-06-04 17:52 ` Nick Drage [this message]
2002-06-04 18:09   ` Ramin Alidousti
     [not found] <scfca615.000@pzsj-office.pzs.com>
2002-06-04 18:48 ` Ramin Alidousti
2002-06-04 19:34   ` Antony Stone
  -- strict thread matches above, loose matches on Subject: below --
2002-06-04 18:35 Brian Ugie
2002-06-04 16:51 Brian Ugie
2002-06-04 17:28 ` Ramin Alidousti

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=20020604185223.T27307@funkyjesus.org \
    --to=nickd@funkyjesus.org \
    --cc=netfilter@lists.samba.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.