I did quite a bit more research on this. Everything I read says an AD DNS should automatically set up those entries. I found a few trouble-shooting documents that suggested checking them, but nothing indicating why they might be wrong, and what to do about it.
I agree that tearing down the domain and re-building it from scratch is the right approach. In the meantime, I returned to my Samba4 project, and found an error I had made on the client side. 5 minutes later my openindiana system successfully joined my Samba4 domain. So at the moment I don't have any real interest in pursuing the Windows Server issue. Thanks for your help. Lee Allen On Fri, Feb 22, 2013 at 11:13 AM, Federico Nan <feder...@nantec.com.ar>wrote: > Maybe you can try to do a setup domain again. > > > 2013/2/22 Lee Allen <l...@leecallen.com> > >> That also fails: >> >> lal...@oi.allenlan.net:~$ host -t SRV _ldap._tcp.allenlan.net. >> Host _ldap._tcp.allenlan.net. not found: 3(NXDOMAIN) >> >> lal...@oi.allenlan.net:~$ host -t SRV _ldap._tcp.dc._msdcs.allenlan.net. >> Host _ldap._tcp.dc._msdcs.ALLENLAN.NET. not found: 3(NXDOMAIN) >> >> I can manually add these records, but according to the MS documentation, >> I shouldn't need to. >> >> Lee Allen >> >> >> >> On Feb 22, 2013 6:40 AM, "Federico Nan" <feder...@nantec.com.ar> wrote: >> >>> You can try to find your record doing: (taking from the official how-to) >>> >>> host -t SRV _ldap._tcp.samdom.example.com. >>> >>> >>> >>> >>> 2013/2/22 Lee Allen <l...@leecallen.com> >>> >>>> This isn't exactly a Samba problem, but I am hoping the experts here can >>>> help me. >>>> >>>> I have been trying to get my OpenIndiana system to join a Samba4 domain >>>> and >>>> I was running into multiple problems. So I decided to test against a >>>> true >>>> Windows Server (2003) domain, to see if there is something wrong with my >>>> client-side setup. >>>> >>>> Attempting to join the WS2003 AD domain also fails. Snooping the >>>> network >>>> traffic reveals this: >>>> >>>> client: DNS query _ldap._tcp.dc._msdcs.ALLENLAN.NET: type SRV, class IN >>>> DC: no such server >>>> >>>> I found this MS link: >>>> http://technet.microsoft.com/en-us/library/cc961719.aspx >>>> >>>> Which says, in part: >>>> >>>> "_ldap._tcp.dc._msdcs.DnsDomainName >>>> Allows a client to locate a domain controller (dc) of the domain named >>>> by >>>> DnsDomainName . All Windows 2000 Server based domain controllers >>>> register >>>> this SRV record." >>>> >>>> I am very new to Active Directory setup. So it is quite likely I have >>>> made >>>> a basic configuration error on the WS2003 AD setup. But true Windows >>>> clients can join the domain successfully. >>>> >>>> Any ideas? >>>> >>>> Does Samba4 automatically put this SRV record into its internal DNS >>>> server? >>>> >>>> Thank you. >>>> >>>> Lee Allen >>>> -- >>>> To unsubscribe from this list go to the following URL and read the >>>> instructions: https://lists.samba.org/mailman/options/samba >>>> >>> >>> > -- *Lee Allen* email: l...@leecallen.com bus: (716) 773-2729 home: (716) 773-2326 cell: (716) 880-0854 fax: (716) 408-8844 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba