From: Ramin Dousti <ramin@cannon.eng.us.uu.net>
To: "Len L." <len@euler.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Blocking access to UDP port 53 (DNS) - Solution
Date: Mon, 11 Aug 2003 14:25:18 -0400 [thread overview]
Message-ID: <20030811182518.GC11900@cannon.eng.us.uu.net> (raw)
In-Reply-To: <12CC60849165134FB7DF8570B621F4D51C89CD@mailxserver.euler.com>
I'm glad it worked but a small note: Is there any standard/RFC specifying
that an MX lookup must come from port 25? Or is it just an arbitrary
observation which works for certain smtp servers and fails for others?
Ramin
On Mon, Aug 11, 2003 at 12:48:22PM -0500, Len L. wrote:
> OK,
> I got it. Here is the rule set I tried and had success (b.t.w. The DNS server is fire walled but is a standalone machine - no forwarding)
> The answer was to reference DNS requests for port 25 only.
> iptables -A INPUT --protocol udp --source-port 25 -s 63.143.210.0/24 -j LOG --log-prefix "XXX LOCAL UDP DNS XXX "
> iptables -A INPUT --protocol udp --source-port 25 -s 63.143.210.0/24 -j ACCEPT
> iptables -A INPUT --protocol udp --source-port 25 -j LOG --log-prefix "XXX EXTERNAL UDP LOG XXX "
> iptables -A INPUT --protocol udp --source-port 25 -j ACCEPT
> iptables -A INPUT -p udp -j LOG --log-prefix "XXX UDP DROP XXX "
> iptables -A INPUT -p udp -j DROP
> Also will drop the 25 sport reference on the internal side along with the logging as a final solution
>
>
> Len Laulainen
>
>
>
prev parent reply other threads:[~2003-08-11 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-11 17:48 Blocking access to UDP port 53 (DNS) - Solution Len L.
2003-08-11 18:25 ` Ramin Dousti [this message]
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=20030811182518.GC11900@cannon.eng.us.uu.net \
--to=ramin@cannon.eng.us.uu.net \
--cc=len@euler.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