[Samba] Invalid zone operation IsSigned

[mark.petersen at markofall.com]

I have two 4.18.9 domain controllers running on my domain, both self compiled on arm64 vanilla Debian 12. - Been running  with version 4.18 for nearly 11 months without issue.

I've added a self compiled 4.20.1 domain controller also running on arm64 Debian 12.

All the the domain controllers are using  BIND9_DLZ for DNS.

All seems to be running fine. samba-tool drs showrepl and samba-tool dbcheck show no errors. Using samba-tool dns query 4.18_or_4.20_server zone -U administrator also shows no errors.

When I use Windows10 RSAT DNS Manager and select the new 4.20 domain controller I see this error on the 4.20 server log:

May 17 15:19:28 fddc20 samba[2179]:   dnsserver: Invalid zone operation IsSigned
May 17 15:19:28 fddc20 samba[2179]: [2024/05/17 15:19:28.706252,  0] ../../source4/rpc_server/dnsserver/dcerpc_dnsserver.c:1076(dnsserver_query_zone)
May 17 15:19:28 fddc20 samba[2179]: [2024/05/17 15:19:28.708257,  0] ../../source4/rpc_server/dnsserver/dcerpc_dnsserver.c:1076(dnsserver_query_zone)
May 17 15:19:28 fddc20 samba[2179]:   dnsserver: Invalid zone operation IsSigned
May 17 15:19:28 fddc20 samba[2179]: [2024/05/17 15:19:28.709796,  0] ../../source4/rpc_server/dnsserver/dcerpc_dnsserver.c:1076(dnsserver_query_zone)
May 17 15:19:28 fddc20 samba[2179]:   dnsserver: Invalid zone operation IsSigned

All of the DNS entries show up correctly on all 3 of the servers, and I cannot detect any other anomaly.

Is this something I should dig into deeper or just an artifact from using the Windows10 tool?

Thanks for any assistance.

Mark