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
title: Recommended and useful mountOptions settings on Azure Files
3
3
description: Learn about the useful and recommended mountOptions settings when you configure the storage class object on Azure Files.
4
-
ms.date: 04/25/2025
4
+
ms.date: 04/27/2025
5
5
ms.reviewer: chiragpa, nickoman, v-leedennis
6
6
ms.service: azure-kubernetes-service
7
7
#Customer intent: As an Azure Kubernetes user, I want to learn about mount option settings so that I can set up my Azure Files storage class object optimally on my Azure Kubernetes Service (AKS) cluster.
@@ -13,54 +13,56 @@ This article discusses recommended mount options when you configure the storage
13
13
14
14
## Recommended settings
15
15
16
-
The following `mountOptions` are recommended for SMB and NFS shares:
16
+
The following `mountOptions`settings are recommended for Server Message Block (SMB) and Network File System (NFS) shares:
- nosharesock # reduces probability of reconnect race
37
+
- actimeo=30 # reduces latency for metadata-heavy workload
38
+
- nobrl # disable sending byte range lock requests to the server and for applications which have challenges with posix locks
39
+
```
40
40
41
-
**NFS shares**
41
+
- **NFS shares**
42
42
43
-
```yaml
44
-
apiVersion: storage.k8s.io/v1
45
-
kind: StorageClass
46
-
metadata:
47
-
name: azurefile-csi-nfs
48
-
provisioner: file.csi.azure.com
49
-
parameters:
50
-
protocol: nfs
51
-
skuName: Premium_LRS # available values: Premium_LRS, Premium_ZRS
52
-
reclaimPolicy: Delete
53
-
volumeBindingMode: Immediate
54
-
allowVolumeExpansion: true
55
-
mountOptions:
56
-
- nconnect=4 # improves performance by enabling multiple connections to share
57
-
- noresvport # improves availability
58
-
- actimeo=30 # reduces latency for metadata-heavy workloads
59
-
```
43
+
```yaml
44
+
apiVersion: storage.k8s.io/v1
45
+
kind: StorageClass
46
+
metadata:
47
+
name: azurefile-csi-nfs
48
+
provisioner: file.csi.azure.com
49
+
parameters:
50
+
protocol: nfs
51
+
skuName: Premium_LRS # available values: Premium_LRS, Premium_ZRS
52
+
reclaimPolicy: Delete
53
+
volumeBindingMode: Immediate
54
+
allowVolumeExpansion: true
55
+
mountOptions:
56
+
- nconnect=4 # improves performance by enabling multiple connections to share
57
+
- noresvport # improves availability
58
+
- actimeo=30 # reduces latency for metadata-heavy workloads
59
+
```
60
60
61
61
> [!NOTE]
62
-
> The location to configure mount options (mountOptions) depends on whether you're provisioning dynamic or static persistent volumes. If you're [dynamically provisioning a volume](/azure/aks/azure-csi-files-storage-provision#dynamically-provision-a-volume) with a storage class, specify the mount options on the storage class object (kind: StorageClass). If you’re [statically provisioning a volume](/azure/aks/azure-csi-files-storage-provision#statically-provision-a-volume), specify the mount options on the PersistentVolume object (kind: PersistentVolume). If you’re [mounting the file share as an inline volume](/azure/aks/azure-csi-files-storage-provision#mount-file-share-as-an-inline-volume), specify the mount options on the Pod object (kind: Pod).
62
+
> The location for configuring mount options (`mountOptions`) depends on whether you provision dynamic or static persistent volumes. If you [dynamically provision a volume](/azure/aks/azure-csi-files-storage-provision#dynamically-provision-a-volume) with a storage class, specify the mount options on the storage class object (`kind: StorageClass`). If you [statically provision a volume](/azure/aks/azure-csi-files-storage-provision#statically-provision-a-volume), specify the mount options on the `PersistentVolume` object (`kind: PersistentVolume`). If you [mount the file share as an inline volume](/azure/aks/azure-csi-files-storage-provision#mount-file-share-as-an-inline-volume), specify the mount options on the `Pod` object (`kind: Pod`).
63
63
64
-
For best practices when using Azure Files, see [Provision Azure Files storage](/azure/aks/azure-csi-files-storage-provision#best-practices).
64
+
## More information
65
+
66
+
For Azure Files best practices, see [Provision Azure Files storage](/azure/aks/azure-csi-files-storage-provision#best-practices).
65
67
66
68
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
Copy file name to clipboardExpand all lines: support/windows-server/active-directory/active-directory-domain-join-troubleshooting-guidance.md
+1-39Lines changed: 1 addition & 39 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,45 +77,7 @@ For more information, see [Domain join error code 0x54b](error-code-0x54b.md).
77
77
78
78
### Error code 0x0000232A
79
79
80
-
Error 0x0000232A is logged when the client computer lacks NetBIOS name resolution to the domain.
81
-
82
-
:::image type="content" source="media/active-directory-domain-join-troubleshooting-guidance/error-0x0000232a-message.png" alt-text="Screenshot of the dialog box showing the error message for error code 0x0000232A.":::
83
-
84
-
Here's an example of the error message:
85
-
86
-
> Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt.
87
-
>
88
-
> The domain name "\<NetBIOS_name\>" might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.
89
-
>
90
-
> If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.
91
-
>
92
-
> The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "\<NetBIOS_name\>":
93
-
>
94
-
> The error was: "DNS server failure."
95
-
> (error code 0x0000232A RCODE_SERVER_FAILURE)
96
-
>
97
-
> The query was for the SRV record for _ldap._tcp.dc._msdcs.\<NetBIOS_name\>
98
-
>
99
-
> Common causes of this error include the following:
100
-
>
101
-
> - The DNS servers used by this computer contain incorrect root hints. This computer is configured to use DNS servers with the following IP addresses:
102
-
>
103
-
> \<ip_address\>
104
-
>
105
-
> - One or more of the following zones contains incorrect delegation:
106
-
>
107
-
> \<NetBIOS_name\>
108
-
> . (the root zone)
109
-
110
-
Here's an example from the *netsetup.log* file:
111
-
112
-
```output
113
-
mm/dd/yyyy hh:mm:ss:ms NetpValidateName: checking to see if '<NetBIOS_name>' is valid as type 3 name
114
-
mm/dd/yyyy hh:mm:ss:ms NetpCheckDomainNameIsValid for <NetBIOS_name> returned 0x54b, last error is 0x0
115
-
mm/dd/yyyy hh:mm:ss:ms NetpCheckDomainNameIsValid [ Exists ] for '<NetBIOS_name>' returned 0x54b
116
-
```
117
-
118
-
When you enter the domain name, make sure you enter the DNS Domain Name rather than the NetBIOS name. For example, if the DNS name of the domain is contoso.com, make sure you enter that name instead of just contoso.
80
+
See [Domain join error code 0x0000232A](error-code-0x0000232a.md) for troubleshooting guide.
description: Provides troubleshooting steps for resolving error code 0x0000232A when you join a workgroup computer to a domain.
4
+
ms.date: 04/25/2025
5
+
manager: dcscontentpm
6
+
audience: itpro
7
+
ms.topic: troubleshooting
8
+
ms.reviewer: eriw,dennhu,herbertm
9
+
ms.custom:
10
+
- sap:active directory\on-premises active directory domain join
11
+
- pcy:WinComm Directory Services
12
+
---
13
+
# Domain join error code 0x0000232A
14
+
15
+
This article provides troubleshooting steps for resolving error code 0x0000232A when you join a workgroup computer to a domain.
16
+
17
+
## Symptoms
18
+
19
+
When you join a workgroup computer to a domain, you receive the following error message:
20
+
21
+
> **Error code 0x0000232A**
22
+
>
23
+
> Computer Name/Domain Changes
24
+
>
25
+
> An Active Directory Domain Controller (AD DC) for the domain "\<NetBIOS\_name>" could not be contacted.
26
+
>
27
+
> Ensure that the domain name is typed correctly.
28
+
>
29
+
> If the name is correct, click Details for troubleshooting information.
30
+
>
31
+
> Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt.
32
+
>
33
+
> The domain name "\<NetBIOS\_name>" might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.
34
+
>
35
+
> If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.
36
+
>
37
+
> The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "\<NetBIOS\_name>":
38
+
> The error was: "DNS server failure." (error code 0x0000232A RCODE\_SERVER\_FAILURE)
39
+
>
40
+
> The query was for the SRV record for \_ldap.\_tcp.dc.\_msdcs.<NetBIOS\_name>
41
+
>
42
+
> Common causes of this error include the following:
43
+
>
44
+
> * The DNS servers used by this computer contain incorrect root hints. This computer is configured to use DNS servers with the following IP addresses:
45
+
> \<ip\_address\>
46
+
> * One or more of the following zones contains incorrect delegation:
47
+
<NetBIOS\_name> . (the root zone)
48
+
49
+
Here's an example from the **netsetup.log** file:
50
+
51
+
```output
52
+
NetpValidateName: checking to see if '<NetBIOS_name>' is valid as type 3 name
53
+
NetpCheckDomainNameIsValid for <NetBIOS_name> returned 0x54b, last error is 0x0
54
+
NetpCheckDomainNameIsValid [ Exists ] for '<NetBIOS_name>' returned 0x54b
55
+
```
56
+
57
+
## Cause
58
+
59
+
Error 0x0000232A indicates that the Domain Name System (DNS) name can't be resolved. The error code can appear with error codes such as RCODE\_NAME\_ERROR and RCODE\_SERVER\_FAILURE, which indicate potential misconfigurations in the DNS settings or root hints. Error 0x0000232A might also occur if the client computer lacks NetBIOS name resolution to the domain.
60
+
61
+
## Troubleshooting steps
62
+
63
+
1. When you enter the domain name, ensure that you enter the DNS domain name rather than the NetBIOS name. For example, if the DNS name of the domain is `contoso.com`, make sure you enter that name instead of `contoso`.
64
+
2. Verify the DNS server settings on the client to ensure they point to the correct DNS server.
65
+
3. In the DNS management console, confirm that the SRV records are correctly registered in DNS for the Active Directory domain controller (DC).
66
+
4. Conduct tests to ensure that DNS queries from the client to the Active Directory Domain Services (AD DS) server are successful after adjustments are made:
67
+
68
+
```console
69
+
nltest /dsgetdc:
70
+
```
71
+
72
+
The expected output should have the DC name as follows:
0 commit comments