Re: The power of default configurations

["Christopher L. Morrow" <christopher.morrow () mci com>]

On Thu, 7 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?
>
> i asked this question of microsoft, in a slightly different form.  (since
> the vast installed based of RFC2136 clients is windows/2k and windows/xp.)
> i wanted to know, why does a client whose address is in RFC1918 address
> space _ever_ send an update to a server that is not in RFC1918 address
> space?  their answer was, many of their large enterprise customers run in
> exactly that configuration, and the defaults have to Just Work in that case.

no to 1) prolong the pain, 2) beat a horsey.. BUT, why are 1918 ips
'special' to any application? why are non-1918 ips 'special' in a
different way?

-Chris