search for: the_lockup_problem

Hi everyone and best wishes for 2023 I think i'm facing the bind 9 DLZ lockup problem described here: https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End#The_Lockup_Problem running samba 4.16 AD on ubuntu 20.04 with bind 9.16.15 there are about 500 computers on the network. quickly after bind restart, DNS response delay increase and reach client timeout (like host or dig on samba host) and named is long to stop. if i disable dlz config on named, there are no d...

On 09/01/2023 14:35, Arnaud FLORENT via samba wrote: > Hi everyone and best wishes for 2023 > > > I think i'm facing the bind 9 DLZ lockup problem described here: > > https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End#The_Lockup_Problem > > > running samba 4.16 AD on ubuntu 20.04 with bind 9.16.15 > > there are about 500 computers on the network. > > > quickly after bind restart, DNS response delay increase and reach client > timeout (like host or dig on samba host) and named is long to stop. >...

...the DCs, the login process sometimes stalls for extended periods of time without even asking for the username. Could DNS be part of the mix? Is using the calls to samba-tool a bad idea? Could this be related to the "lockup problem"? https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End#The_Lockup_Problem Would that be different if I use nsupdate vs samba-tool? Would I be better off with the internal DNS? If I switch to the internal DNS, are existing zones and entries transferred? Thanks for any insights and best wishes, Christian