Skip to content

Commit c04cb6c

Browse files
authored
Merge pull request #78899 from cephalin/issue26915
#26915
2 parents b1a1f79 + a29b65a commit c04cb6c

File tree

1 file changed

+10
-2
lines changed

1 file changed

+10
-2
lines changed

articles/app-service/overview-inbound-outbound-ips.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.workload: web
1212
ms.tgt_pltfrm: na
1313
ms.devlang: na
1414
ms.topic: article
15-
ms.date: 04/20/2018
15+
ms.date: 06/06/2019
1616
ms.author: cephalin
1717
ms.custom: seodec18
1818

@@ -32,7 +32,15 @@ Regardless of the number of scaled-out instances, each app has a single inbound
3232
- Delete the last app in a resource group _and_ region combination and recreate it.
3333
- Delete an existing SSL binding, such as during certificate renewal (see [Renew certificates](app-service-web-tutorial-custom-ssl.md#renew-certificates)).
3434

35-
## Get static inbound IP
35+
## Find the inbound IP
36+
37+
Just run the following command in a local terminal:
38+
39+
```bash
40+
nslookup <app-name>.azurewebsites.net
41+
```
42+
43+
## Get a static inbound IP
3644

3745
Sometimes you might want a dedicated, static IP address for your app. To get a static inbound IP address, you need to configure an [IP-based SSL binding](app-service-web-tutorial-custom-ssl.md#secure-a-custom-domain). If you don't actually need SSL functionality to secure your app, you can even upload a self-signed certificate for this binding. In an IP-based SSL binding, the certificate is bound to the IP address itself, so App Service provisions a static IP address to make it happen.
3846

0 commit comments

Comments
 (0)