[SSSD-users] 1.11.5 ddns failure on Ubuntu 14.04[SOLVED]
longina at sdu.dk
Tue Jun 24 09:02:19 UTC 2014
Hi again, thanks a lot!
What about service discovery mechanism in SSSD?
I could expect, that the AD services advertise themselves and for SSSD this is the base for finding the right way to establish
connection to the DC/DNS or whatever.
In our Enterprise we have AD DNS and split DNS. Clients contact split DNS for resolve addresser - so I can not
configure client to refer directly to AD DNS.
My client(with SSSD) has to find out who runs AD DNS for dyndns updates, and by now it contacts the wrong server.
Does it use information from resolvconf?
How can I manually find out which serveres advertise dyndns service?
From: sssd-users-bounces at lists.fedorahosted.org [mailto:sssd-users-bounces at lists.fedorahosted.org] On Behalf Of steve
Sent: 23. juni 2014 16:06
To: sssd-users at lists.fedorahosted.org
Subject: Re: [SSSD-users] 1.11.5 ddns failure on Ubuntu 14.04[SOLVED]
On Mon, 2014-06-23 at 13:52 +0000, Longina Przybyszewska wrote:
> /etc/resolv.conf is overwritten af:
> root at skywalker:/home-local/longinap# cat /etc/resolv.conf # Dynamic
> resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
> # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
> nameserver 127.0.1.1
OK. Now we're getting somewhere. That's not going to get you to an AD dns server.
Set the dns to the same server which the windows boxes use. Remove dnsmasq if it's up and set /etc/nsswitch.conf to:
hosts: files dns
I'm guessing Ubuntu. So look here:
If not, do it the old way in:
sssd-users mailing list
sssd-users at lists.fedorahosted.org
More information about the sssd-users