Skip to content

Commit 291f4c8

Browse files
author
Paul D.Smith
committed
Trying to raise the Acrolinx score.
1 parent a4b0545 commit 291f4c8

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

articles/operator-nexus/troubleshoot-dns-issues.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -12,30 +12,30 @@ ms.date: 12/10/2024
1212

1313
# Troubleshoot Nexus DNS Issues
1414

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.
1616

1717
## Diagnosis
1818

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.
2323

2424
## Mitigation steps
2525

2626
Follow these steps for mitigation.
2727

2828
### 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+
```
3535

3636
## Verification
3737

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.
3939

4040
## Related content
4141

0 commit comments

Comments
 (0)