Skip to content

Commit a4b0545

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

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,14 +12,14 @@ 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 Service) error in NNF can mean that Azure resources cannot be contacted which impacts deployment or managment of some new name for Nexus Far Edge resources.
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.
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 Resource) or similar Azure resource. Errors observed include but are not limited to:
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:
2020
* "...could not login to OCI registry..."
2121
* "GatewayTimeout".
22-
* Azure portal shows no errors being generated for the Azure resources that canot be reached; this is because the failing operations are not actually accessing the resources at all.
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.
2323

2424
## Mitigation steps
2525

@@ -35,7 +35,7 @@ Follow these steps for mitigation.
3535

3636
## Verification
3737

38-
After the DNS cache has been refreshed, create/manage operations are successful.
38+
After the DNS cache has been refreshed, create or manage operations are successful.
3939

4040
## Related content
4141

0 commit comments

Comments
 (0)