Skip to content

Commit b9268fd

Browse files
authoredApr 26, 2022
Added a link to the script
Added a link to the script - Run the script with username and password
1 parent e6c3d28 commit b9268fd

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed
 

‎articles/hdinsight/domain-joined/troubleshoot-domainnotfound.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Cluster creation fails with DomainNotFound error in Azure HDInsight
33
description: Troubleshooting steps and possible resolutions for issues when interacting with Azure HDInsight clusters
44
ms.service: hdinsight
55
ms.topic: troubleshooting
6-
ms.date: 01/23/2020
6+
ms.date: 04/26/2022
77
---
88

99
# Scenario: Cluster creation fails with DomainNotFound error in Azure HDInsight
@@ -35,9 +35,9 @@ When the domain joined clusters are deployed, HDI creates an internal user name
3535
* Deploy an Ubuntu VM in the same subnet and domain join the machine
3636
* SSH into the machine
3737
* sudo su
38-
* Run the script with username and password
38+
* Run the [script](./sample-script.md) with username and password
3939
* The script will ping, create the required configuration files and then domain. If it succeeds, your DNS settings are good.
4040

4141
## Next steps
4242

43-
[!INCLUDE [troubleshooting next steps](../includes/hdinsight-troubleshooting-next-steps.md)]
43+
[!INCLUDE [troubleshooting next steps](../includes/hdinsight-troubleshooting-next-steps.md)]

0 commit comments

Comments
 (0)