Notice: This resource is no longer being actively maintained and as a result some information may be out of date or inaccurate. Please see for technical instructions or for support related concerns.
RUN@cloud » Custom Application Domains

Custom Application Domains

Last modified by Michael Neale on 2014/08/05 03:55

Custom Application Domain Names

By default, applications deployed on RUN@Cloud will be assigned a hostname based on the application name and your CloudBees username. If you already own an Internet domain that you previously purchased from a domain provider (like, you can setup your application to use your custom domain instead of the default domain.

If you are using SSL you can do it with your SSL revproxy service IP address too. 

Configuring a custom application domain

Step 1 - (for non SSL apps)

To use your domain with CloudBees you'll need to update your domain's DNS record to point to your application's default domain name using a CNAME record. The tools for doing this will vary based on the DNS provider you use to manage your domain, but most providers should have some kind of web interface for creating a new CNAME record.

For example, let's assume I own the domain, and I want to this custom domain for my application that currently uses the default domain I would need to goto my DNS provider's web interface and add a new CNAME for and set its value to


After updating your DNS record, you will need to wait for the DNS entry to propagate, which can take up to a day, but usually not more than an hour. After your DNS record has propogated, doing an nslookup command for should then return the name

# nslookup

Step 1 - (for SSL apps)

When you create your SSL revproxy service - you will be assigned an IP. That IP will be used to access your apps. Any app "bound" to your SSL revproxy will be accessed ONLY via that IP. The app default url mentioned above ( will no longer be used or operational. 

To use this - set up an A record for any domain names you want to point to your app - pointing to  the IP address of your SSL revproxy.

Step 2 - Update your application configuration

Once your custom domain is setup to forward to the domain (using a CNAME), you need to reconfigure your application to use as a custom domain name.

  • Login to the console
  • Select your application
  • Open the configuration tab
  • Add your custom domain name to the domain name aliases text box
  • Click the save button
  • After your application is automatically redeployed, all requests to will be forwarded to your CloudBees application.

You can also use the command line: bees app:proxy:update  -a APPLICATION_ID  --alias,

Multiple domains

If you with to have multiple domain names associated with your app - comma delimit them in your configuration: 


NON SSL: A-record/apex/naked domain for your application

If you are using an SSL revproxy - you can ignore this section. You can use your IP (it belongs to you as long as you keep that SSL revproxy around). You are free to use A records and apex's. 

One limitation of DNS is that you can only use CNAMES for subdomains - so, for example, if you own the domain "" for your app - you would have to put a CNAME for to If you want "" to go to your application - you can't use a CNAME - only an A record.  


1) Put an A record for the apex (root) to an IP that "" resolves to on lookup 

2) Use a service like DNSSimple ALIAS record for your domain that will create the A record and keep it updated for you. 

3) Use a redirection service that tells clients that go to to redirect to (you will note this is what, etc do) **.

The downside of #1 above is that is that YOU are responsible for keeping the A record IP address up to date - if that IP becomes unavailable or changes, you have to update it yourself (however it is quickest to start with). If you do this - please use a CNAME with a subdomain as well and ideally use that when you can (the naked one can be "for vanity" purposes). 

~** they don't direct literally to, but you know what I mean emoticon_wink

Wildcard domains

Wildcard domains (* are not supported by default, but this can be enabled for paid applications if you file a support ticket.  Be sure to include the wildcard pattern you'd like on your account when you file the ticket.

Naked domain redirection - redirect to

Preliminary notes

  • It is not a good practice to publish a web site on 2 different hostnames (e.g. and, it will have negative impact on Search Engine Optimization. The best practices is to publish a web site on 1 single hostname (e.g. and to do a redirection from 1 domain to the other (e.g. redirect to This should be a 301 Permanent Redirect.
  • We recommend on CloudBees platform to not map applications to naked domains (e.g. and instead to map applications to subdomains (e.g. because naked domain do not support CNAME records.

Here are docs of various DNS providers on how to configure a naked domain redirection

Created by Michael Neale on 2011/07/19 23:15