All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aleksandar Milivojevic <amilivojevic@pbl.ca>
To: Jason Opperisano <opie@817west.com>
Cc: Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: Re: nat and dns
Date: Thu, 23 Sep 2004 09:34:11 -0500	[thread overview]
Message-ID: <4152DEE3.6010007@pbl.ca> (raw)
In-Reply-To: <1095948833.1750.9.camel@wolfpack.ljm.dom>

Jason Opperisano wrote:
> find me a response to a client resolver request that doesn't fit in a
> single UDP packet, and i'll stop seeing red every time i see someone
> recommend allowing TCP 53 from any IP to their DNS server (*).

Theoretically (since I don't know of any such implementation), it is 
perfectly legal to have resolver library that first tries TCP, and than 
UDP :-P

Of course, such approach would be waste of network resources (sending 
one UDP datagram one way, and another the other way is usually at least 
as fast as only establishihg new TCP connection without sending any data 
through it).

Anyhow, I don't see why are you going red when you see TCP port 53 open? 
  If it is possible for random internet site to fetch zone from DNS 
server, it is misconfiguration of DNS server, not of the firewall.  OSI 
layers and all that stuff, you know ;-).  If your DNS server does not 
allow you to restrict who can do zone transfers, that you should 
seriously consider switching to different DNS server that does.  It is 
the same as if you were to restrict one directory on HTTP server to only 
certain range of IP addresses, and than blame it on firewall when you 
misconfigure HTTP server.

-- 
Aleksandar Milivojevic <amilivojevic@pbl.ca>    Pollard Banknote Limited
Systems Administrator                           1499 Buffalo Place
Tel: (204) 474-2323 ext 276                     Winnipeg, MB  R3T 1L7


  reply	other threads:[~2004-09-23 14:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-23  9:00 nat and dns Raphael Jacquot
2004-09-23 10:34 ` Nick Drage
2004-09-23 11:09   ` Samuel Díaz García
2004-09-23 11:23     ` Nick Drage
2004-09-23 13:01       ` Samuel Díaz García
2004-09-23 13:19       ` Alexis
2004-09-23 14:13       ` Jason Opperisano
2004-09-23 14:34         ` Aleksandar Milivojevic [this message]
2004-09-23 14:44           ` Jason Opperisano
2004-09-23 15:09             ` Aleksandar Milivojevic
2004-09-24  9:43         ` Jozsef Kadlecsik
2004-09-23 13:17     ` Alexis
2004-09-23 14:09     ` Aleksandar Milivojevic
2004-09-23 12:00   ` Raphael Jacquot
2004-09-23 14:17 ` Aleksandar Milivojevic
2004-09-23 22:02   ` Dimitar Katerinski
2004-09-23 22:16     ` Jason Opperisano
2004-09-24  1:56     ` Aleksandar Milivojevic
2004-09-24  6:51       ` Jason Opperisano
     [not found] <20020829192902.29524.97535.Mailman@kashyyyk>
2002-09-11 12:10 ` NAT and DNS Mauricio Gouvea
2002-09-11 13:10   ` 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=4152DEE3.6010007@pbl.ca \
    --to=amilivojevic@pbl.ca \
    --cc=netfilter@lists.netfilter.org \
    --cc=opie@817west.com \
    /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.