Hi
Den 13 mars 2018 12:09 skrev "Max DiOrio" :
> Is your dns server set to secure updates only?
>
Yes it is and as is should be.
I've filed a bugreport on the package at Ubunts launchpad so hopefully it
gets resolved before release of 18.04.
On Tue, Mar 13, 2018, 5:4
After som serious digging I caved in and upgraded dnsutils on my Ubuntu.
Seems that the future Ubuntu 18.04 has a non-working install of nsupdate.
When upgrading to version 9.12 nsupdate (using ISC PPA) everything started
to work.
2018-03-09 19:24 GMT+01:00 Roger Martensson :
> Hi!
>
&
Hi!
Setup: Ubuntu 18.04 (future), SSSD 1.16.0, nsupdate/bind: 9.11.2.P1, 2008R2
DC/DNS
I need some help and guidance with troubleshooting nsupdate-problems.
I get the famous "TSIG error with server: tsig verify failure" when trying
to update my A-record against our Microsoft DNS.
I get the error
lidate_tgt] (0x0400): TGT verified using key
for [MYCLIENT$@DOMAIN1.EXAMPLE.COM].
2018-03-05 16:18 GMT+01:00 Roger Martensson :
> I've always used a fully qualified hostname. My example was a cleanup
> version and I was to lazy to write subdomain1.example.com.
>
> I've set ad_
omain name. But still hade the same problems as before.
Increading debug_level created an amazing amount of rows. :)
This is my clean up log.
2018-03-05 15:35 GMT+01:00 Sumit Bose :
> On Mon, Mar 05, 2018 at 08:40:19AM -0500, Justin Stephenson wrote:
> > On 03/05/2018 08:25 AM, Rog
In search for a solution on an another problem I upgraded från 1.13 to
1.15.3. This seem to have solved this 'cache-problem'.
2018-03-02 15:54 GMT+01:00 Roger Martensson :
> Hi!
>
> OS: Ubuntu 16.04, SSSD: 1.13.4
>
> I'm seeing something that has me wondering if I
'krb5_validate = false' but that disables some
nice security measure.
So.. Anyone that can help me back on track? AKA What did I do wrong this
time?
2018-03-05 14:13 GMT+01:00 Roger Martensson :
> Hi!
>
> It's me again with multiple domain problems. :)
>
> I have once again
Hi!
It's me again with multiple domain problems. :)
I have once again problems with multiple domain. This time with login.
Maybe some one of you could explain to me what I did wrong this time.
OS: Ubuntu 17.10
SSSD: 1.15.3
Domain setup. two subdomain both connected to the same parent domain Bot
t; 1. Has no idea from which domain the mount request coming from (it
> only sees – hey, mount /a/b for me)
>
> 2. Can be used for other mounts, not just user home areas so it
> does not make much sense here either
>
>
>
> Ondrej
>
>
>
> *From:*
Hi!
OS: Ubuntu 16.04, SSSD: 1.13.4
I'm seeing something that has me wondering if I have missunderstood
anything. (quite possible)
I have multi domain Active Directory forest. I have a client connected to
subdomain1 using SSSD and can do ID-query in both subdomain1 and subdomain2.
If I have a us
Hi!
I'm experiencing something that I'm not sure is as expected or not.
First some data:
OS: Ubuntu 16.04
SSSD Version: 1.13.4
I have managed to set up a SSSD against a AD-subdomain. NSS-lookup works.
Can use 'userid', 'use...@subdomain1.domain.tld' and UPN when looking up an
ID.
I have set up
11 matches
Mail list logo
