在SciLinux 7.1（EL7.1）框中join运行在Windows 2008R2 64位上的AD域。
遵循“红帽企业Linux 7 Windows集成指南”：
$ sudo realm discover -v mems.local * Resolving: _ldap._tcp.mems.local * Resolving: mems.local ! Discovery timed out after 15 seconds mems.local type: kerberos realm-name: MEMS.LOCAL domain-name: mems.local configured: no 然而：
$ nslookup -type=srv _ldap._tcp.mems.local Server: 172.17.21.20 Address: 172.17.21.20#53 _ldap._tcp.mems.local service = 0 100 389 mwinds2.mems.local. _ldap._tcp.mems.local service = 0 100 389 mwinds1.mems.local.
现在我该怎么做？
# realm join mems.local See: journalctl REALMD_OPERATION=r1063.5453 realm: Cannot join this realm # journalctl REALMD_OPERATION=r1063.5453 -- Logs begin at Wed 2015-07-29 14:50:27 AKDT, end at Wed 2015-07-29 15:08:25 AKDT. -- Jul 29 15:08:10 playbox.mems.local realmd[5456]: * Resolving: _ldap._tcp.mems.local Jul 29 15:08:20 playbox.mems.local realmd[5456]: * Resolving: mems.local Jul 29 15:08:25 playbox.mems.local realmd[5456]: * No results: mems.local # nslookup _ldap._tcp.mems.local Server: 172.17.21.20 Address: 172.17.21.20#53 *** Can't find _ldap._tcp.mems.local: No answer # nslookup -type=srv _ldap._tcp.mems.local Server: 172.17.21.20 Address: 172.17.21.20#53 _ldap._tcp.mems.local service = 0 100 389 mwinds2.mems.local. _ldap._tcp.mems.local service = 0 100 389 mwinds1.mems.local. $ tcping mwinds1 389 mwinds1 port 389 open.
有人绊倒这个问题，这里是什么修复了我的Ubuntu 14.04框，我的域名保持超时。
编辑/etc/nsswitch.conf：
使主机行看起来像这样 –
hosts: files dns mdns4_minimal [NOTFOUND=return] mdns4
然后再次尝试你的发现。
你在使用NetworkManager吗？ IIRC什么领域发现做的是查询NM的D-Bus接口的DHCP域。
我只想尝试领域直接joinmems.local，这是否工作？