Connecting to ActiveDirectory without DNS

TrueNAS General
1

Dear all,

For a month we where trying to configure AD on TrueNAS server (CE, 27).

We have two difficulties:

  • We are on the separated network from institutional AD server
  • Institutional AD is not the DNS

Is there a way to bypass these problems?

We are part of big institution, and we can’t ask for changing configurations of host AD

2

Why are you using a pre-pre-release version of TrueNAS? TN 26 isn’t even released yet, much less 27.

3

Not really. AD works via DNS. If your institution allows you to set up a secondary DNS server and pull at least these zones from the AD DC(s):

  • your.ad.domain
  • _msdcs.your.ad.domain

Then point your NAS at that secondary server only - things might work. But you still need Kerberos and LDAP communication to the DC(s) - so why would they allow that and not DNS?

HTH,
Patrick

4

Sorry, a mistype, I meant 25.

5

@pmh, it’s how they setup the configuration. Thanks for the info, I will see if I can negotiate the secondary server.

6

Is it samba requirement or TrueNAS requirement?

My institution already have an DNS, separated from AD and several samba servers that works quite well.

Digging through logs, the configuration blocks at this command:

net -d 0 -S ulg.ac.be --json --option realm=ulg.ac.be ads info
Didn't find the ldap server!

If we execute the same without forcing the server, it works:

net -d 0 --json --option realm=ulg.ac.be ads info 
{"LDAP server": ....

So, why TrueNAS forces the server, and is there a way to not force it?