[79412] in North American Network Operators' Group
Re: The power of default configurations
daemon@ATHENA.MIT.EDU (JP Velders)
Wed Apr 6 18:16:51 2005
Date: Thu, 7 Apr 2005 00:15:51 +0200 (CEST)
From: JP Velders <jpv@veldersjes.net>
To: Sean Donelan <sean@donelan.com>
Cc: nanog@merit.edu
In-Reply-To: <Pine.GSO.4.58.0504061756550.5174@clifden.donelan.com>
Errors-To: owner-nanog@merit.edu
> Date: Wed, 6 Apr 2005 18:00:05 -0400 (EDT)
> From: Sean Donelan <sean@donelan.com>
> To: nanog@merit.edu
> Subject: The power of default configurations
> On Mon, 4 Apr 2005, Paul Vixie wrote:
> > adding more. oh and as long as you're considering whether to restrict
> > things to your LAN/campus/ISP, i'm ready to see rfc1918 filters deployed...
> Why does BIND forward lookups for RFC1918 addresses by default? Why isn't
> the default not to forward RFC1918 addresses (and martian addresses). If
> a sysadmin is using BIND in a local network which uses RFC1918 address,
> those sysdmins can change their configuration?
RFC1918 space is space you can use inside of an organization in the
same way you could use non-RFC1918 space. If a program would treat it
differently that would only make sense if that program could only be
used in such a way that it would *have* to treat it differently.
Regards,
JP Velders
