On Mon, 2014-06-23 at 09:09 +0000, Longina Przybyszewska wrote:
Ok. 2 cases:
- The first server is the server chosen automatically by service discovery - obviously doesn't answer.
Hi Narrow it down. Set the primary dns on your client to be a dns server which you know for certain is handling your ad domain. For now remove other dns entries and strip sssd of anything apart from ad.
/etc/hosts 127.0.0.1 catral.hh3.site catral localhost
/etc/resolv.conf search hh3.site nameserver 192.168.1.16
sssd.conf [sssd] services = nss, pam config_file_version = 2 domains = hh3.site [nss] [pam] [domain/hh3.site] id_provider = ad access_provider = ad auth_provider = ad ldap_id_mapping = false
e.g. here is an openSUSE client running 1.11.5 joined to the domain hh3.site. The DC at 192.168.1.16 is also running bind for this domain. A session on catral with a common error;)
catral:/home/steve # nsupdate -g
update delete catral.hh3.site. in A send
tkey query failed: GSSAPI error: Major = Unspecified GSS failure. Minor code may provide more information, Minor = Ticket expired. catral:/home/steve # kinit -kt /etc/krb5.keytab CATRAL$ catral:/home/steve # nsupdate -g
update delete catral.hh3.site. in A send update add catral.hh3.site. 3600 in A 192.168.1.25 send quit
catral:/home/steve # nslookup catral Server: 192.168.1.16 Address: 192.168.1.16#53 Name: catral.hh3.site Address: 192.168.1.25
If you haven't got the dns exactly right, you may need some tweaks in sssd.conf to get you there: http://linuxcostablanca.blogspot.com.es/2014/05/sssd-autofs-with-ad-backend....
HTH Steve