OS X clients (seen this with 10.13.6), that are AD joined will trigger unsuported DNS update requests: [2020/11/16 15:10:42.626088, 0] ../../source4/dns_server/dns_update.c:419(handle_one_update) Can't handle updates of type 255 yet (type 255 is TYPE_ANY). I don't have a network sniff or more information yet.
Interestingly enough, looking at source4/dns_server/dns_update.c:handle_one_update() We have: 406 switch (update->rr_type) { 407 case DNS_QTYPE_A: 408 case DNS_QTYPE_NS: 409 case DNS_QTYPE_CNAME: 410 case DNS_QTYPE_SOA: 411 case DNS_QTYPE_PTR: 412 case DNS_QTYPE_MX: 413 case DNS_QTYPE_AAAA: 414 case DNS_QTYPE_SRV: 415 case DNS_QTYPE_TXT: 416 break; 417 default: 418 DEBUG(0, ("Can't handle updates of type %u yet\n", 419 update->rr_type)); 420 return DNS_ERR(NOT_IMPLEMENTED); 421 } But then later in that function: 572 } else if (update->rr_class == DNS_QCLASS_ANY) { 573 if (update->rr_type == DNS_QTYPE_ALL) { So it looks like (rr_class == DNS_QCLASS_ANY && rr_type == DNS_QTYPE_ALL) should be added as a supported case in the switch statement above, as we have code to deal with it.
Created attachment 16360 [details] fix you're right, attached patch fixes the problem.
Comment on attachment 16360 [details] fix LGTM. Why don't you run this through a gitlab MR for testing.
This bug was referenced in samba master: 18d68e85c8a1ef7fd570d3d3fd4dde484aea417e