The last version of Bind9 mentioned in Samba is 9.12, can someone update the required files: named.conf.dlz, sambadns.py and whatever creates the dlz_bind9_xx.so files. I believe I could update the first two myself, but have no idea how to do the last one.
Thanks for pointing this out. Looks like no one is trying AD with newer BIND releases. I will add support for released 9.x versions.
Rowland, would you be able to test provisioning using one of the recent versions of BIND? Hopefully there are no configuration file changes in any of the newer versions. I haven't gone through all the changelogs yet. The patches are here: https://gitlab.com/samba-team/samba/-/merge_requests/1569 Amitay.
(In reply to Amitay Isaacs from comment #2) You appear to be adding the bind development branches and not adding up to the latest version (yes, I know that no distro is using these yet, but they will) From the Bind website: 9.11 esv 9.12 stable 9.13 development 9.14 stable 9.15 development 9.16 esv 9.17 development 9.18 stable 9.19 development 9.20 esv 9.21 development It looks to myself that Bind is now using the odd numbers as a development base and when they think it is stable they rename it as an even number, do we want to support 'development' versions ?
I have added all the versions which are available for download. The latest version you can download is 9.17.4. I cannot add support for future versions without looking at the source to figure out if the dlz api has been modified. I am happy to drop development versions (less patches).
(In reply to Amitay Isaacs from comment #4) Fair comment, I suppose you cannot depend on things not changing, but as I said, do we want to support development versions ? From my point of view, they seem to be like using a git version of Samba, okay for testing things, but would you use it in production ?
(In reply to Rowland Penny from comment #5) Let's keep only the stable and ESV releases. I will update the patch set.
This bug was referenced in samba master: cdb6c5d1eca1c0f6967941dbd1da07be6b53d302 95278618829227632b2bcb29fc272e600607ea41 a167a2154d4909e8e1f97d9f36d0e4c947f2d944 016c1174ef783990f93e348ee82f5c989c43cbbf 4d09797652059c3ed5b2a4f94f2181ce14d39972 ca3c18a236dedfdfbf225dcfcd0418f1634d8759 5b2ccb1c7cad5cded5dad37a18a7d42c1680b2f7 1bccc67ce7c6364a95fbfeb095938522671578a8
Created attachment 16263 [details] Patches for v4-13, v4-12 and v4-11
Hi Karolin, This is ready for 4.13 and 4.12 (and 4.11 if there will be another bug fix release). Thanks...
(In reply to Martin Schwenke from comment #9) Hi Martin, pushed to autobuild-v4-{13,12}-test. Thanks! Karolin
This bug was referenced in samba v4-12-test: 4cbeb5ca3c387b9d893e729e339db1a9adbf03b4 49eaec78a0b977663c84fd4c96fd7c6fc0a731d6 5400b928d426af5dc56234ce110a3871d88c015d 55d1f4e9f5ee1b0a57f86414f5e1698994a55b6c 4ab29fb056aebe4c6c6783e673a9f80f46c9e200 7336a1c67550281627b108a402b36c675c5247ce 8a7fc998f0930145d74aa5e32ae67ae4bd996af0 fd5ef942badd63cd21f267d73665c068f777140b
This bug was referenced in samba v4-13-test: 8e2ef3cda23b5d7988533ec37d25ecc7fe27efb9 b5bc60e77d393b7deb55ba64f519ce91cd0cc265 63d94da74a6592a8e465dda4c3b85c9024d9af46 4e65cc6058e35e8b99c80be839d73dbadfea05c9 345137381553ccdcaf1fd3831049172a4818a5f7 f6b6867d5497d2805346fe28efadb3ba63fc3d97 a831cc5799bac57d5d5b7f6c3327b8c6f27874a4 24ae26cb49e63405c0f7bf56ef38fc7988c969a7
Closing out bug report. Thanks!
This bug was referenced in samba v4-13-stable (Release samba-4.13.2): 8e2ef3cda23b5d7988533ec37d25ecc7fe27efb9 b5bc60e77d393b7deb55ba64f519ce91cd0cc265 63d94da74a6592a8e465dda4c3b85c9024d9af46 4e65cc6058e35e8b99c80be839d73dbadfea05c9 345137381553ccdcaf1fd3831049172a4818a5f7 f6b6867d5497d2805346fe28efadb3ba63fc3d97 a831cc5799bac57d5d5b7f6c3327b8c6f27874a4 24ae26cb49e63405c0f7bf56ef38fc7988c969a7
This bug was referenced in samba v4-12-stable (Release samba-4.12.10): 4cbeb5ca3c387b9d893e729e339db1a9adbf03b4 49eaec78a0b977663c84fd4c96fd7c6fc0a731d6 5400b928d426af5dc56234ce110a3871d88c015d 55d1f4e9f5ee1b0a57f86414f5e1698994a55b6c 4ab29fb056aebe4c6c6783e673a9f80f46c9e200 7336a1c67550281627b108a402b36c675c5247ce 8a7fc998f0930145d74aa5e32ae67ae4bd996af0 fd5ef942badd63cd21f267d73665c068f777140b