From: Nick Drage <nickd@funkyjesus.org>
To: I <netfilter@lists.samba.org>
Subject: Re: dns server
Date: Sat, 8 Jun 2002 10:58:57 +0100 [thread overview]
Message-ID: <20020608105857.I2090@funkyjesus.org> (raw)
In-Reply-To: <1023372279.8475.27.camel@billy.demon.nl>; from tonni@billy.demon.nl on Thu, Jun 06, 2002 at 04:04:38PM +0200
On Thu, Jun 06, 2002 at 04:04:38PM +0200, Tony Earnshaw wrote:
> tor, 2002-06-06 kl. 15:22 skrev Corin Langosch:
<snip>
> It depends what you want to do with it. And what DNS software you're
> running. I.e., if it's BIND, you can do more with BIND 9 than you can
> with BIND 8, more with BIND 8 than with BIND4.
>
> Many security people might say that if you're running BIND 4 or 8, then
> you shouldn't be. Some of them again might say that you should be
> running BIND 9.2.
I believe that the latest BIND 8.something is still OK, and version 8 is
being maintained as far as security patches go.
As for the rest of the thread, you're best restricting that kind of access
using named.conf as the problem is at layer 7 - the BIND application, not
layer 3 - where netfilter mostly lives.
--
FunkyJesus System Administration Team
next prev parent reply other threads:[~2002-06-08 9:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 13:22 dns server Corin Langosch
2002-06-06 13:31 ` Francois Peyron
2002-06-06 13:37 ` Raymond Leach
2002-06-06 13:45 ` Maciej Soltysiak
2002-06-06 13:48 ` Raymond Leach
2002-06-06 14:00 ` Antony Stone
2002-06-06 14:36 ` Arne Sagnes
2002-06-06 15:06 ` Tony Earnshaw
2002-06-06 13:33 ` Antony Stone
2002-06-06 14:00 ` Daniel Bastos
2002-06-06 14:04 ` Tony Earnshaw
2002-06-08 9:58 ` Nick Drage [this message]
2002-06-09 7:40 ` Tony Earnshaw
-- strict thread matches above, loose matches on Subject: below --
2002-06-08 10:21 Corin Langosch
2002-06-08 22:36 ` Nick Drage
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=20020608105857.I2090@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox