From: "Brian Ugie" <bugie@pzs.com>
To: netfilter@lists.samba.org
Subject: iptables and DNS
Date: Tue, 04 Jun 2002 09:51:31 -0700 [thread overview]
Message-ID: <scfc8dba.094@pzsj-office.pzs.com> (raw)
Hi,
I am hoping that someone can explain the role that DNS has in
relation to iptables and if there is a way to stop iptables from
resolving.
I have a network where a netscreen firewall sits in front or our
servers. We map public IPs to the servers and do initial port filtering
from the netscreen. We also want to have each machine filter just in
case the windows box gets compromised ;). It has seemed to me that
iptables will not first use /etc/hosts to resolve but will go straight
to the DNS server. Is this a valid statement? nsswitch.conf lists file
first. Since DNS will resolve the server to a public address but it is
actually on a private address, iptables get confused and the net result
is long delays on ssh and ftp logins and server time outs on DNS
queries.
To test my theory I set the DNS record to the private ip and that
worked like a champ. I feel that I am left with only the option to
create views in bind.
Has anyone else out there seen this or know of a better solution?
Thanks in advance,
Brian
next reply other threads:[~2002-06-04 16:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 16:51 Brian Ugie [this message]
2002-06-04 17:28 ` iptables and DNS Ramin Alidousti
-- strict thread matches above, loose matches on Subject: below --
2002-06-04 17:41 Brian Ugie
2002-06-04 17:52 ` Nick Drage
2002-06-04 18:09 ` Ramin Alidousti
2002-06-04 18:35 Brian Ugie
[not found] <scfca615.000@pzsj-office.pzs.com>
2002-06-04 18:48 ` Ramin Alidousti
2002-06-04 19:34 ` Antony Stone
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=scfc8dba.094@pzsj-office.pzs.com \
--to=bugie@pzs.com \
--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.