From ca52871541bb0303e1b07b7c105424f67bd1c804 Mon Sep 17 00:00:00 2001 From: Andrew Bartlett Date: Fri, 4 Nov 2011 08:45:49 +1100 Subject: s4-setup Remove servicePrincipalName: DNS/${DNSDOMAIN} from new installations This servicePrincipalName is incorrect (windows does not use that servicePrincipalName, as it targets the server it is updating, not the root of the DNS tree), and now that we have multiple DNS backends that use the internal database, it is quite incorrect (as it cannot exist on more than one account). Andrew Bartlett Autobuild-User: Andrew Bartlett Autobuild-Date: Thu Nov 10 01:11:46 CET 2011 on sn-devel-104 --- source4/setup/provision_dns_add_samba.ldif | 1 - 1 file changed, 1 deletion(-) (limited to 'source4/setup/provision_dns_add_samba.ldif') diff --git a/source4/setup/provision_dns_add_samba.ldif b/source4/setup/provision_dns_add_samba.ldif index 6c664d910b..7fb2e78961 100644 --- a/source4/setup/provision_dns_add_samba.ldif +++ b/source4/setup/provision_dns_add_samba.ldif @@ -12,6 +12,5 @@ userAccountControl: 512 accountExpires: 9223372036854775807 sAMAccountName: dns-${HOSTNAME} servicePrincipalName: DNS/${DNSNAME} -servicePrincipalName: DNS/${DNSDOMAIN} clearTextPassword:: ${DNSPASS_B64} isCriticalSystemObject: TRUE -- cgit