Updating through knsupdate is no problem at all. With knsupdate I can actually update bind9 and knot. The problem is with the script somehow working for bind and not working for knot.

Any ideas why knot doesn't write anything to syslog?

Knot is started with systemd. I just restarted knot with Now I do get somewhat more log entries but no logging for failed updates. When I use the correct key knot logs an successful update, but with a wrong key nothing is logged although the client receives a BadKey response. /Ulrich Jan Včelák &lt;jan.vcelak(a)nic.cz <mailto:jan.vcelak@nic.cz>> schrieb am Mi., 7. Okt. 2015 um 19:36 Uhr: Hi Ulrich. On Tuesday, October 06, 2015 07:26:25 AM Ulrich Wisser wrote: The configuration looks fine. It works for me. Are you running systemd? Which version of Knot DNS do you have? Is it a version from packages or a custom built one? Regards, Jan -- Ulrich Wisser ulrich(a)wisser.se <mailto:ulrich@wisser.se> _______________________________________________ knot-dns-users mailing list knot-dns-users(a)lists.nic.cz https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users

Hello Ulrich. On Wednesday, October 07, 2015 08:59:50 PM Ulrich Wisser wrote: wrong We just discussed this with the rest of the team. And we agreed that logging of the failures would be useful. It will be implemented soon. Here is the ticket: https://gitlab.labs.nic.cz/labs/knot/issues/431 Cheers, Jan --

Yes, I am working hard on that :-) D On 10/08/2015 11:33 AM, Ulrich Wisser wrote: Great! How about the key name being the same as the zone name. Will that be fixed too? /Ulrich Jan Včelák &lt;jan.vcelak(a)nic.cz&gt; schrieb am Do., 8. Okt. 2015 um 10:56 Uhr: Ulrich Wisser ulrich(a)wisser.se _______________________________________________ knot-dns-users mailing listknot-dns-users@lists.nic.czhttps://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users _______________________________________________ knot-dns-users mailing list knot-dns-users(a)lists.nic.cz https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users

Hi Ulrich, It seems there is a specific problem with the dname compression in the TSIG processing. Compression is the difference between knsupdate and the Python script. As a workaround, you could try to set a different key name. Dan On 10/05/2015 09:29 PM, Ulrich Wisser wrote: Hi! In the last few days I have tried a new service for DDNS, nsupdate.info. I have some problems with the service and I have been able to reproduce the problem in a small sample script. The attached script does update my bind9 instance but reports SERVFAIL for Knot. Unfortunately I still have not been able to get Knot to write more extensive log entries. The script uses the Python dns library from Nominum. This is the output of the script (first update to bind then to knot) $ python example.py performing add for name ddns.example.com and origin example.com with rdtype A and ipaddr 2.3.4.5 performing add for name ddns.example.com and origin example.com with rdtype A and ipaddr 2.3.4.5 DNS error [SERVFAIL] performing add for name ddns.example.com and origin example.com with rdtype A and ipaddr 2.3.4.5 Knot didn't log anything at all. (Any hints for that config would be welcome.) Bind did log the following Oct 5 21:07:49 localhost named[23792]: client beef::cafe#59322/key example.com: updating zone 'example.com/IN': adding an RR at ' ddns.example.com.' A Some error in the script? Could someone point me to a working script? Any hints are welcome! Kind regards from Stockholm Ulrich -- Ulrich Wisser ulrich(a)wisser.se _______________________________________________ knot-dns-users mailing listknot-dns-users@lists.nic.czhttps://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users _______________________________________________ knot-dns-users mailing list knot-dns-users(a)lists.nic.cz https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users