no SRV records found fail!

[meltman]

I'm having an issue getting freenas 9.10.1 to join an AD domain. I see the following in the debug.log.

Code:

Sep  6 20:21:33 nas1 manage.py: [common.freenasldap:1150] FreeNAS_ActiveDirectory_Base.get_SRV_records: looking up SRV records for _ldap._tcp.dc._msdcs.corp.demo.software

Sep  6 20:21:33 nas1 manage.py: [common.freenasldap:1162] FreeNAS_ActiveDirectory_Base.get_SRV_records: no SRV records for _ldap._tcp.dc._msdcs.corp.demo.software found, fail!

Sep  6 20:21:33 nas1 manage.py: [common.freenasldap:12] Traceback (most recent call last):

Sep  6 20:21:33 nas1 manage.py: [common.freenasldap:12]   File "/usr/local/www/freenasUI/../freenasUI/common/freenasldap.py", line 1152, in get_SRV_records

Sep  6 20:21:33 nas1 manage.py: [common.freenasldap:12]     answers = resolver.query(host, 'SRV')

Sep  6 20:21:33 nas1 manage.py: [common.freenasldap:12]   File "/usr/local/lib/python2.7/site-packages/dns/resolver.py", line 981, in query

Sep  6 20:21:33 nas1 manage.py: [common.freenasldap:12]     raise_on_no_answer, source_port)

Sep  6 20:21:33 nas1 manage.py: [common.freenasldap:12]   File "/usr/local/lib/python2.7/site-packages/dns/resolver.py", line 910, in query

Sep  6 20:21:33 nas1 manage.py: [common.freenasldap:12]     raise NXDOMAIN

Sep  6 20:21:33 nas1 manage.py: [common.freenasldap:12] NXDOMAIN

At the same time though, I can run the host command and get an output:

Code:

[root@nas01] ~# host -t srv _ldap._tcp.dc._msdcs.corp.demo.software

_ldap._tcp.dc._msdcs.corp.demo.software has SRV record 0 100 389 ad01.corp.demo.software.

[root@nas01] ~# nslookup ad01.corp.demo.software

Server: 172.16.50.5

Address:       172.16.50.5#53



Name:  ad01.corp.demo.software

Address: 172.16.50.5



[root@nas01] ~#

Can anyone see anything glaring that I'm doing wrong? It seems that the freeNas box can in fact see the srv record but at the same time it acts as if it can't.

 

[dlavigne]

Is this on 9.10.1? If so, it is worth creating a bug report at bugs.freenas.org and posting the issue number here.

 

[meltman]

Issue #17368 created.

Thanks for the guidance. Looking forward to figuring this one out.

 

[meltman]

The issue is actually fixed in the 9.10 nightly track. I was able to successfully join. I'd like to remain in the stable track though.