We have a TrueNas that stopped working this AM and won’t connect to local AD. We can ping the AD from the TrueNas device. Both have been rebooted. Tried everything we can think of, but no progress.
If there anyone that is available to provide paid assistance?
It may be that you’re getting hit with this issue. If this is the case then ther’s currently no solution to the problem… If it’s a different problem you may have to provide additional information for anyone to help (there’s propably no one on this forum that provides paid help, since we’re all just “users”).
Hi and welcome to the forums.
What version are you running?
Can you share anymore details about the errors you are seeing.
Hi,
@LarsR Thanks, I asked because the previous poster mentioned a patch that worked (at least for him). Re-reading, it looks like the patch is to the source code and requires recompiling.
@Johnny_Fartpants it’s v25.10.0. Similar error to the poster in the link I replied to: “The DNS response does not contain an answer to the question: [hostname]@[my.ad.domain]” and I can verify that query is being sent to my AD DNS server:
13:02:51.000281 IP [HOSTNAME.AD.MY.DOMAIN].37449 > [AD.MY.DOMAIN].domain: 61836+ A? [HOSTNAME]@[AD.MY.DOMAIN] (38)
Assuming this is a production server as it sounds fairly urgent?
May I suggest you roll back to 25.04.2.5 as this is still considered to be the most stable version as per the software status.
Nothing at all wrong with trying the latest version and having a play but when in production I would seriously suggest people use the software status as a guide. Personally I even stay a bit behind the Mission Critical guidance sometimes.
Yes, the fix need recompiling, there is no workaround for now.
I think you can wait for the next bugfix which I hope will contain a fix for this.
(My ticket has not being screened for now)
That’s what I did. Unfortunately before I discovered the AD problem, I upgraded my ZFS pools. So I installed 25.04, joined AD successfully, then imported the pools. So far so good.
Thank you!
