LUA-AXFR-SCRIPT documentation does not match behaviour in 4.1 #6228
Comments
Looks like a regression, possibly introduced in #5250. |
Still present in 4.1.1. Returncode 0 leads to an exception, leaving us unable to filter out records during transfer. For our sub zones this is an issue, cause many queries go to the wrong name servers (which we intent to filter out). Is there any workaround at present or a timeframe for a fix? Thanks, Ronny |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Short description
The feature
LUA-AXFR-SCRIPT
in 4.1 is not consistent with documentation and seems to lack the possibility to actually filter out records.0
does not actually work.Environment
Steps to reproduce
example.com
on a different server and allow axfr to the test systemon the test system:
pdnsutil create-slave-zone example.com <master-ip>
create a file
/etc/powerdns/test.lua with
contents like in https://doc.powerdns.com/md/authoritative/modes-of-operation/pdnsutil set-meta example.com LUA-AXFR-SCRIPT /etc/powerdns/my.lua
pdns_control retrieve example.com
Problem 1: missing parentheses in the example
Logs:
record:qname:
withrecord:qname():
inmy.lua
and try again:Problem 2: Return code 0 ist not actually allowed
Logs:
pdns/pdns/lua-auth4.cc
Lines 115 to 121 in 4e6b74f
1
:Problem 3: Records can only be appended to, but not modified/ignored
if we check the database the record has been added, not replaced like we originally intended:
Long story short:
LUA-AXFR-SCRIPT
axfrfilter
can currently not actually filter records, only append(*) if that turns out to be the case, apologies in advance!
The text was updated successfully, but these errors were encountered: