Inbound IPs

Last Updated October 2014

To use custom domains on Pagoda Box, you'll need an IP to point your DNS A-record to. Your can use Pagoda Box's public IPs or you add dedicated IPs to your app. This is great for any application that needs a dedicated IP or SSL. After reading this doc, you should be familiar with:

  • Managing Inbound IPs
  • Adding dedicated inbound IP addresses to your app
  • Enjoying all the goodness that comes with your own inbound IPs

Pagoda Box Public IP Addresses

Whenever you use a custom domain on your app, you need to point the A-record of that domain to an IP. If your app doesn't need SSL, you're free to use any or all of the available public IPs.

The list of public IPs can be found in your dashboard under Network > Inbound IP Addresses. Each public IP belongs to a Pagoda Box endpoint located in different datacenters around the world. While your app is hosted in a single datacenter, these global endpoints will route all requests to your application.

*A domain can have multiple A-records. Each A-record is pointed to a single IP. When a request is made to your domain, your DNS provider will route the request to the nearest IP listed in your A-records. Really, there's no reason not to tie all of the public IPs to DNS A-records.

Not All DNS Providers Support Multiple A-Records

Whether or not you're able to have multiple A-records for a single IP depends on your DNS Provider. Not All DNS Providers Support Multiple IPs for a Single A-Record. Please review your DNS provider's documentation to see if this option is available.

Perks

Globally Distributed Endpoints & Improved Load Times

Having IPs located around the world will improve load times for global customers. It should be noted that this is not a replacement for a CDN. Requests to Pagoda Box public IPs are routed through the gigabit backbone that connects our datacenters, but network latency will still add to load times. However, file-transfer rates will be greatly improved.

Dedicated Inbound IP Addresses

Pagoda Box allows you to add dedicated inbound IP addresses to each of your apps. These IPs are unique to your app. Adding a dedicated IP is simple and using them has some significant perks.

Adding a Dedicated Inbound IP

Pagoda Box allows you to add dedicated inbound IP addresses to each of your apps. These IPs are unique to your app. Adding a dedicated IP is simple and using them has some significant perks.

Next, select the datacenter in which you would like the IP to reside. It's best to select a datacenter closest to your target market. This will reduces load times. You can have multiple dedicated IPs in your app, either in the same datacenter or completely different datacenters. Once selected, click "Save" and a dedicated IP will be added to your app.

An IP's Datacenter Cannot Be Changed

Once set, an IP's datacenter cannot be changed. In order to have an IP in another datacenter, you'll have to create a new dedicated IP.

Using Dedicated Inbound IPs

Any dedicated inbound IPs added to your app are available for use. Simply point the A-record of one or more of your DNS Aliases your dedicated IP(s). Once DNS changes have propagated, your dedicated IP(s) will be in use.

Perks

SSL

A dedicated inbound IP is required to install an SSL certificate on your app. The Adding SSL documentation provides more information about installing SSL certificates.

DDoS Protection

In many cases, DDoS attacks target a single IP. There are systems in place to mitigate these attacks, but if a public Pagoda Box IP is targeted, some apps may be affected. Using a dedicated IP address will isolate your app from these effects.

DDoS Attacks Directed at Your IP

If your dedicated inbound IP is the target of a DDoS attack, your IP will be quarantined, potentially causing your app to be unavailable until the attack subsides.

Globally Distributed SSL & Improved Load Times

Having dedicated IPs located around the world allows you globally distribute application endpoints encrypted with SSL. It will improve load times for global customers. It should be noted that this is not a replacement for a CDN. Requests to dedicated IPs are routed through the gigabit backbone that connects our datacenters, but network latency will still add to load times. However, file-transfer rates will be greatly improved.

If you have any questions, suggestions, or corrections, let us know.