Skip to content

Commit 21dcc18

Browse files
committed
minor edits
1 parent 436d68a commit 21dcc18

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/cloud-shell/faq-troubleshooting.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -121,12 +121,12 @@ command that requires elevated permissions.
121121
- `*.servicebus.windows.net`
122122
- `*.servicebus.usgovcloudapi.net` for Azure Government Cloud
123123

124-
### Accessing Cloud Shell from subnet that uses a private DNS resolver - Failed to request a terminal
124+
### Failed to request a terminal - Accessing Cloud Shell from a network that uses a private DNS resolver
125125

126126
- **Details**: Cloud Shell uses Azure Relay for terminal connections. Cloud Shell can fail to
127127
request a terminal due to DNS resolution problems. This failure can be caused when you launch a
128128
Cloud Shell session from a host in a network that has a private DNS Zone for the servicebus
129-
domain. This can also happen if you are using a private on-premises DNS server.
129+
domain. This error can also occur if you're using a private on-premises DNS server.
130130

131131
- **Resolution**: You can add a DNS record for the Azure Relay instance that Cloud Shell uses.
132132

@@ -171,7 +171,7 @@ command that requires elevated permissions.
171171
Address: 40.84.152.91
172172
```
173173

174-
1. Add an A record for the public IP in the Private DNS Zone of the VNET isolated setup. For this
174+
1. Add an A record for the public IP in the Private DNS Zone of your private network. For this
175175
example, the DNS record would have the following properties:
176176

177177
- Name: ccon-prod-southcentralus-aci-02

0 commit comments

Comments
 (0)