Hello,
attached you will find 2 files which will reproduce the error on my server.
The funny thing is, that named crashes, if you use he line:
allow-update { key ddns; "ADservers"; "lan"; };
But with
allow-update { key ddns; "lan"; "ADservers"; };
it runs. So I can use my old configuration, if I change the order of the
address list of allow-update. Very strange.
I hope, you can reproduce the error now.With kind regards. Christian Motschke -----Ursprüngliche Nachricht----- Von: Maximiliano Curia [mailto:[EMAIL PROTECTED] Gesendet: Sonntag, 12. Oktober 2008 21:21 An: [EMAIL PROTECTED] Betreff: Bug#501800: Please, provide a full example of the bug tags 501800 +moreinfo thank you I have tried to reproduce this bug with the following named.local: key "key-test" { algorithm hmac-md5; secret "IVqRBcWBoPU2LhJTFnaJrw=="; }; acl "test" { 192.168.0.0/24; }; acl "another" { 192.168.1.0/24; }; zone "example.com" { type master; file "/etc/bind/db.local"; allow-update { key key-test; "test"; "another"; }; check-names ignore; }; And it seems to work. Could you please provide a minimal named.conf.local that triggers this bug? Anyway, in the 9.5.0 release sources the file KNOWN-DEFECTS documents an ugly bug, and an untested patch. It might be worth checking if appling the patch fixes your problem. -- A computer scientist is someone who, when told to "Go to Hell," sees the "go to," rather than the destination, as harmful. Saludos /\/\ /\ >< `/
named.conf.options.test
Description: named.conf.options.test
named.conf.local.test
Description: named.conf.local.test
