Displaying 4 results from an estimated 4 matches for "dyndni".
Did you mean:
dyndns
2024 Dec 17
1
Error when joining new DC
AFAIK sssd on RHEL is by default doing dyndny updates and it needs to be disabled in the config. Same for a Windows.
Instead of client configuration which can be changed by any sysadmin I prefer to deny DNS updates centrally, where I have control.
Br
________________________________
From: samba <samba-bounces at lists.samba.org> on behalf of Rowland Penny via samba <samba at
2024 Dec 17
1
Error when joining new DC
On Tue, 17 Dec 2024 05:54:55 +0000
Peter Mittermayer via samba <samba at lists.samba.org> wrote:
> AFAIK sssd on RHEL is by default doing dyndny updates and it needs to
> be disabled in the config. Same for a Windows.
That is easy to fix, there is no reason to use sssd with Samba, it is
pointless, so, on redhat:
systemctl stop sssd
systemctl disable sssd
>
> Instead of client
2024 Dec 16
1
Error when joining new DC
On Mon, 16 Dec 2024 17:42:33 +0000
Peter Mittermayer via samba <samba at lists.samba.org> wrote:
> I really would like to do that. That's exactly why I'm asking if DNS
> update can be allowed for DCs only and denied for all other clients.
> I looked into it a few years ago but did not find a (simple) solution
> to this.
>
> Br
>
You seem to be conflating the
2024 Dec 17
1
Error when joining new DC
If not using sssd, how do you join the clients to the domain? We are not using GPO, only user authentication and DNS.
Due to security restrictions we are not able to install Samba packages on all the clients. Sssd is the simplest solution, and the only one recommended and officially supported by RedHat.
Br
________________________________
From: samba <samba-bounces at lists.samba.org> on