samba - Nov 2022 - accidentally upgraded DC to 4.17.3 ... didn't work

Forgive my flooding, but I really search for a solution and would like 
to avoid downgrading again.

Compared the ouput of

ps axf | egrep "samba|smbd|winbindd"

on both DCs. Yes, different samba-versions.

adc1, samba 4.16.6:

     938 ?        S      0:00  \_ samba: tfork waiter process(941)
     941 ?        S      0:04  |   \_ samba: task[winbindd] pre-fork master
     946 ?        S      0:00  |       \_ samba: tfork waiter process(950)
     950 ?        Ss     0:39  |           \_ /usr/sbin/winbindd -D 
--option=server role check:inhibit=yes --foreground
    1125 ?        S      0:03  |               \_ winbindd: domain child 
[ARBEITSGRUPPE]
    1128 ?        S      0:03  |               \_ winbindd: idmap child


adc2, samba 4.17.3:

    6203 ?        S      0:00  \_ samba: tfork waiter process(6205)
    6205 ?        S      0:00  |   \_ samba: task[winbindd] pre-fork master
    6209 ?        S      0:00  |       \_ samba: tfork waiter process(6218)
    6218 ?        Ss     0:00  |           \_ /usr/sbin/winbindd -D 
--option=server role check:inhibit=yes --foreground
    6229 ?        S      0:00  |               \_ winbindd: domain child 
[ARBEITSGRUPPE]


here that "idmap child" process is missing.

Is that OK? good or bad?

So far I always checked stuff like "wbinfo -u" after upgrades and 
interpreted a working output as "things went OK".

I think I solved it.

Completely uninstalled samba-related packages and dependent libraries 
and stuff and installed fresh from bullseye-backports.

did:

apt-get install  -t bullseye-backports  acl attr samba 
samba-dsdb-modules samba-vfs-modules winbind libpam-winbind 
libnss-winbind krb5-config krb5-user dnsutils

Seems to work now.
phew

side note:

# host -t A  adc2.arbeitsgruppe.my.tld

host: error while loading shared libraries: libdns-9.16.33-Debian.so: 
cannot open shared object file: No such file or directory

Can't find that file on

https://packages.debian.org/

-

I now also upgraded one domain member server. Same picture.

I had to remove "samba-common  samba-common-bin  samba-libs" extra,
and
run "autoremove" ... that removed

"libnss-winbind libpam-winbind libsmbclient python3-samba samba 
samba-common samba-common-bin samba-dsdb-modules samba-libs 
samba-vfs-modules smbclient winbind"

After that installing again from backports. -> works so far

*phew*

I will keep it like this for today and wait for feedback.

The other DC and the second domain member (=fileserver) tomorrow.