Hi Daniel. Yes, I changed the storage directory to other location with right permissions, and now the logs said: 2016-08-22T17:52:21 info: [manojitos.cl] zone loader, semantic check, completed 2016-08-22T17:52:21 info: [manojitos.cl] loaded, serial 2016010416 -> 2016010417 2016-08-22T17:52:21 info: [manojitos.cl] NOTIFY, outgoing, 200.1.123.7@53: serial 2016010417 2016-08-22T17:52:22 info: [manojitos.cl] IXFR, outgoing, 200.1.123.7@16933: incomplete history, fallback to AXFR 2016-08-22T17:52:22 info: [manojitos.cl] AXFR, outgoing, 200.1.123.7@16933: started, serial 2016010417 2016-08-22T17:52:22 info: [manojitos.cl] AXFR, outgoing, 200.1.123.7@16933: finished, 0.00 seconds, 1 messages, 3820 bytes So there's no error. Thanks a lot. Can I suggest to improve the previous error log? Maybe if it can say "bad permission" instead of "not enough memory" could be better to administrators :)

Best, Hugo On 08/22/2016 01:22 PM, daniel.salzman(a)nic.cz wrote: > Hi, > > You have the storage directory under /etc. I suspect the server is not > allowed to create a zone journal file there. The journal is important > for IXFR. > Could you verify that? In such a case you can configure proper > zone.file location > but different zone.storage directory. > > Daniel > > On 2016-08-22 16:18, Hugo Salgado wrote: >> Hi Daniel. Here I'm attaching my .conf. >> >> Thanks a lot! >> >> Hugo >> >> On 08/22/2016 05:46 AM, Daniel Salzman wrote: >>> Hi Hugo, >>> >>> I can't reproduce your problem. Could you send me your configuration >>> file >>> please? Don't forget to mangle sensitive information, like TSIG key. >>> >>> Thank you, >>> Daniel >>> >>> On 08/19/2016 07:57 PM, Hugo Salgado wrote: >>>> Hi. >>>> I have a KNOT master with a small zone (32 records), which is >>>> logging an >>>> error after the secondary (BIND) tries to update the zone. AFAIK, >>>> Bind >>>> tries with IXFR first, but my master says: >>>> >>>> 2016-08-19T16:32:12 error: [manojitos.cl] IXFR, outgoing, >>>> 200.1.123.7@29095: failed to start (not enough memory) >>>> >>>> After that the secondary retries with AXFR, and that works: >>>> >>>> 2016-08-19T16:32:12 info: [manojitos.cl] AXFR, outgoing, >>>> 200.1.123.7@13644: started, serial 2016011013 >>>> 2016-08-19T16:32:12 info: [manojitos.cl] AXFR, outgoing, >>>> 200.1.123.7@13644: finished, 0.00 seconds, 1 messages, 2573 bytes >>>> >>>> The error is the same the first time I provision the zone in the >>>> secondary as in following updates. Is there a bug in the error >>>> message, >>>> or should I worry for some memory requirement in my server (or >>>> service)? >>>> >>>> I'm with Knot 2.3.0 on a FreeBSD 10.3-release-p7. The secondary is >>>> not >>>> under my administration, but I was told is Bind with an up-to-date >>>> version. >>>> >>>> Thanks! >>>> >>>> Hugo >>>> >>>> _______________________________________________ >>>> knot-dns-users mailing list >>>> knot-dns-users(a)lists.nic.cz >>>> https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users >>>