I understand that you are receiving this error:
"The security database on the server does not have a computer account for this workstation trust relationship."
I encountered a similar scenario recently where a customer was able to resolve this issue by deleting and re-establishing the AADDS and AD trust.
It's also possible that you are encountering this error during authentication due to a limitation that prevents AAD DC administrators from enabling name suffix routes. If this is the case, you can use the TrustedDomain\SamAccountName syntax for authentication as a workaround.
Let me know if this helps and if you still encounter this issue.
If the information helped you, please Accept the answer. This will help us as well as others in the community who may be researching similar questions. Otherwise let us know if you have further questions.