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
______________________________________________________________________________________________ knot-dns-users mailing list knot-dns-users@lists.nic.cz https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users
knot-dns-users mailing list
knot-dns-users@lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users