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: articles/operator-nexus/troubleshoot-dns-issues.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,30 +12,30 @@ ms.date: 12/10/2024
12
12
13
13
# Troubleshoot Nexus DNS Issues
14
14
15
-
Nexus Network Fabric (NNF) provides a bridge between some new name for Nexus Far Edge resources and Azure but a DNS (Domain Name System) error in NNF can mean that Azure resources can't be contacted which impacts deployment or management of some new name for Nexus Far Edge resources.
15
+
NNF (Nexus Network Fabric) NNF provides a bridge between some new name for Nexus Far Edge resources and Azure, accessing Azure resources via their domain names. However a DNS (Domain Name System) error in NNF can mean that Azure resources can't be contacted which impacts deployment or management of some new name for Nexus Far Edge resources.
16
16
17
17
## Diagnosis
18
18
19
-
* Deployment or management of remote Nexus resources fails with "DeploymentFailed", often because of a failure to access an ACR (Azure Container Registry) or similar Azure resource. Errors observed include but are not limited to:
20
-
* "...could not login to OCI registry..."
21
-
* "GatewayTimeout".
22
-
* Azure portal shows no errors being generated for the Azure resources that can't be reached; this is because the failing operations are not actually accessing the resources at all.
19
+
* Deployment or management of remote Nexus resources fails with "DeploymentFailed", often because of a failure to access an ACR (Azure Container Registry) or similar Azure resource. Errors observed include but aren't limited to:
20
+
* "...could not login to OCI registry..."
21
+
* "GatewayTimeout".
22
+
* Azure portal shows no errors being generated for the Azure resources that are unreachable; there are no errors because the failing operations aren't actually accessing the resources at all.
23
23
24
24
## Mitigation steps
25
25
26
26
Follow these steps for mitigation.
27
27
28
28
### Trigger a DNS cache refresh for the NNF Workload Proxy
29
-
30
-
```bash
31
-
az login
32
-
az account set --subscription <SUBSCRIPTION>
33
-
az resource tag --tags exampleTag=exampleValue --name <CLUSTER> --resource-group <CLUSTER_RG> --resource-type "Microsoft.ContainerService/managedClusters"
34
-
```
29
+
30
+
```bash
31
+
az login
32
+
az account set --subscription <SUBSCRIPTION>
33
+
az resource tag --tags exampleTag=exampleValue --name <CLUSTER> --resource-group <CLUSTER_RG> --resource-type "Microsoft.ContainerService/managedClusters"
34
+
```
35
35
36
36
## Verification
37
37
38
-
After the DNS cache has been refreshed, create or manage operations are successful.
38
+
After the DNS cache is refreshed, create or manage operations are successful.
0 commit comments