You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/linux/sql-server-linux-active-directory-join-domain.md
+25-5Lines changed: 25 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,19 +23,27 @@ Before you configure Active Directory authentication, you need to set up an Acti
23
23
> [!IMPORTANT]
24
24
> The sample steps described in this article are for guidance only and refer to Ubuntu 16.04, Red Hat Enterprise Linux (RHEL) 7.x and SUSE Enterprise Linux (SLES) 12 operating systems. Actual steps may slightly differ in your environment depending on how your overall environment is configured and operating system version. For example, Ubuntu 18.04 uses netplan while Red Hat Enterprise Linux (RHEL) 8.x uses nmcli among other tools to manage and configure network. It is recommended to engage your system and domain administrators for your environment for specific tooling, configuration, customization, and any required troubleshooting.
25
25
26
+
### Reverse DNS (RDNS)
27
+
28
+
When you set up a computer running Windows Server as a domain controller, you might not have a RDNS zone by default. Ensure that an applicable RDNS zone exists for both the domain controller and the IP address of the Linux machine that will be running SQL Server.
29
+
30
+
Also ensure that a PTR record that points to your domain controllers exists.
31
+
26
32
## Check the connection to a domain controller
27
33
28
-
Check that you can contact the domain controller with both the short and fully qualified names of the domain:
34
+
Check that you can contact the domain controller by using both the short and the fully qualified names of the domain, and by using the hostname of the domain controller. The IP of the domain controller also should resolve to the FQDN of the domain controller:
29
35
30
36
```bash
31
37
ping contoso
32
38
ping contoso.com
39
+
ping dc1.contoso.com
40
+
nslookup <IP address of dc1.contoso.com>
33
41
```
34
42
35
43
> [!TIP]
36
44
> This tutorial uses **contoso.com** and **CONTOSO.COM** as example domain and realm names, respectively. It also uses **DC1.CONTOSO.COM** as the example fully qualified domain name of the domain controller. You must replace these names with your own values.
37
45
38
-
If either of these name checks fail, update your domain search list. The following sections provide instructions for Ubuntu, Red Hat Enterprise Linux (RHEL), and SUSE Linux Enterprise Server (SLES) respectively.
46
+
If any of these name checks fail, update your domain search list. The following sections provide instructions for Ubuntu, Red Hat Enterprise Linux (RHEL), and SUSE Linux Enterprise Server (SLES) respectively.
39
47
40
48
### Ubuntu 16.04
41
49
@@ -139,11 +147,15 @@ Use the following steps to join a SQL Server host to an Active Directory domain:
139
147
```base
140
148
sudo yum install realmd krb5-workstation
141
149
```
142
-
143
-
**SUSE:**
150
+
151
+
**SLES 12:**
152
+
153
+
Note that these steps are specific for SLES 12, which is the only officially supported version of SUSE for Linux.
@@ -156,6 +168,14 @@ Use the following steps to join a SQL Server host to an Active Directory domain:
156
168
157
169
1. After you confirm that your DNS is configured properly, join the domain by running the following command. You must authenticate using an AD account that has sufficient privileges in AD to join a new machine to the domain. This command creates a new computer account in AD, creates the **/etc/krb5.keytab** host keytab file, configures the domain in **/etc/sssd/sssd.conf**, and updates **/etc/krb5.conf**.
158
170
171
+
Because of an issue with **realmd**, first set the machine hostname to the FQDN instead of to the machine name. Otherwise, **realmd** might not create all required SPNs for the machine and DNS entries won't automatically update, even if your domain controller supports dynamic DNS updates.
172
+
173
+
```bash
174
+
sudo hostname <old hostname>.contoso.com
175
+
```
176
+
177
+
After running the above command, your /etc/hostname file should contain <oldhostname>.contoso.com.
0 commit comments