[Pdns-users] Re: AXFR's in powerdns

[Norbert Sendetzky]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 22 June 2003 18:48, you wrote:
> On 2003-06-22 at 18:32, Norbert Sendetzky wrote:
> > No, disable-axfr implies that it is enabled by default, but you
> > can disable it if you want to. This is because default values of
> > config variables are mostly "no", especially if you name
> > something "disable-...".
>
> To me, disable-axfr set to true clearly implies that axfr is
> disabled. This is not what happens.

That's right, but I wanted to mention that if you name an option 
disable-... and the default value is "no", it is activated by default 
(until you set it to "yes").

If you name something enable-... and defaults are "no" then you do not 
want to provide this functionality (perhaps for security reasons) 
until the user enables it and hopefully knows what he is doing.

The other thing you are pointing to is the reversed (false) behaviour 
introduced by the new axfr checking code. I still explained the 
correction in my other mail (cut the "!" in the first if statement).


Norbert


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE+9eOUxMLs5v5/7eARAknDAJ0YshaialbJkkzaurlimHNnVeTf9gCfZE2O
0L+9UetwolFyuhKpKqAO8Ls=
=VJ2W
-----END PGP SIGNATURE-----