I want to reuse my existing domain (managed by IBM Hursley, but that shouldnt matter I think) with my new Bluemix website. What should I ask the team who manages my domain name and what I have to set in the Bluemix app/site?
Thanks,
Pimmy
To integrate the answer from #umberto-manganiello you can also setup on your Registrar DNS configuration an 'A' Record instead of a 'CNAME' record, and making it to refer to the following IP addresses according to the Bluemix region where your application is running:
US-SOUTH: 75.126.81.68
EU-GB: 5.10.124.142
AU-SYD: 168.1.35.169
This solution actually is working better that the CNAME one.
Edit Aug 24th 2016:
the IBM Bluemix platform added the following hostnames in order to allow customers to setup their custom domains (used with their IBM Bluemix applications) as CNAME of the following hostnames
US South: secure.us-south.bluemix.net
United Kingdom (EU-GB): secure.eu-gb.bluemix.net
Sydney (AU-SYD): secure.au-syd.bluemix.net
The customers now can use the right hostname as CNAME value of their custom domain, according to the IBM Bluemix region their applications are running on
To do this you have to perform two steps:
First is the configuration on Bluemix:
From your Bluemix Dashboard, click your org's dropdown and choose Manage Organizations. Then click domains, and add domain. The domain is organization wide, which means you can link different subdomains to different applications. This can be useful if you have different components (e.g: blog, web application, web service).
Once you’ve created the custom domain go back to your dashboard and select an application. Then on top you'll see a “Routes” label followed by a pencil icon (Edit routes and App Access). Click on the pencil button and add a route for www.yourdomain.com.
Second is the DNS settings and URL forwarding you'll need on your existing domain.
Now that Bluemix side is all set, ask your domain manager to forward yourdomain.com to www.yourdomain.com and to add a CNAME record in DNS settings which points www.yourdomain.com to the appname.mybluemix.net that BlueMix provides by default.
If you need additional information please take a look at Bluemix Docs - Creating and using a custom domain
Here is an example:
My app name in Bluemix = askwatsonto
My route in Bluemix = askwatsonto.mybluemix.net
My domain name = askwatsonto.com
My org = carlos.ferreira#something.com
Steps using the CF CLI:
Download CF CLI: https://console.ng.bluemix.net/docs/cli/index.html#downloads
Add your domain to your org: $cf create-domain carlos.ferreira#something.org askwatsonto.com
Add route to your app: $cf map-route askwatsonto www.askwatsonto.com
Add CNAME to your DNS provider. I used domainmonster.com:
My application was deployed in US-South. Use a different address for the following other regions:
US-SOUTH: secure.us-south.bluemix.net
EU-GB: secure.eu-gb.bluemix.net
AU-SYD: secure.au-syd.bluemix.net'
Debug DNS using this web site http://simpledns.com/lookup-dg.aspx
Read the doc: https://console.ng.bluemix.net/docs/manageapps/updapps.html#domain
Related
Background
I have two websites:
- web1.azurewebsites.net
- web2.azurewebsites.net
I have added a traffic manager called webtm.trafficmanager.net.
web1.azurewebsites.net is configured with a custom domain web.example.com. I've also added a wildcard SSL certificate to it (i.e., *.example.com). If I request web.example.com it serves the website without any issues.
Requirement
I need to setup Traffic Manager on top of these two sites. So, if web1.azurewebsites.net is down/offline, then Traffic Manager can switch to web2.azurewebsites.net automatically.
Implementation question
I've read these SO answers (SO 1, SO 2) and this docs article, however, I have some doubts. I would really appreciate if someone can confirm my understanding outlined below, please?
Step 1: I understand that I'll have to update DNS records to something like: web.example.com. 60 IN CNAME webtm.trafficmanager.net.. Remove other DNS/CNAME records that point web.example.com to web1.azurewebsites.net.
Step 2: I'll need to remove the current custom domain mapping from web1.azurewebsites.net and then re-add it. Set custom domain to web.example.com and the CNAME configuration will show the traffic manager endpoint. No DNS changes required in this step?
Step 3: Add a custom domain to web2.azurewebsites.net set the custom domain to web.example.com and the CNAME configuration will show the traffic manager endpoint. No DNS changes required in this step?
Step 4: No changes to the SSL certificate added to web1.azurewebsites.net.
Step 5: Add the SSL certificate to web2.azurewebsites.net.
Now, accessing https://web.example.com should hit the traffic manager. It will see that web1.azurewebsites.net is online, so it will direct users to that. If web1.azurewebsites.net goes down, it will auto redirect users to web2.azurewebsites.net.
Thanks!
Your steps are mostly correct. What you want to do is to follow this document---Configure a custom domain name in Azure App Service with Traffic Manager integration
In step 3 and step 4, the traffic manager domain name will show under CNAME configuration. Select it and click Add custom domain. No other steps are required.
If a record is already in use and you need to preemptively bind your
apps to it, you can create an additional CNAME record. For example, to
preemptively bind www.contoso.com to your app, create a CNAME record
from awverify.www to contoso.trafficmanager.net. You can then add
www.contoso.com to your app without the need to change the www
CNAME record. For more information, see Migrate an active DNS name to
Azure App Service.
You also could see the full steps in this blog. In this blog, it uses a second web app in a different subscription, so it selects an external endpoint for that. If your first web app and your Traffic Manager instance are in the same subscription, use an Azure Endpoint, as you would normally, and choose the web app in that subscription.
Let me know if you face any questions.
I've recently bought a domain name, and I'm trying to redirect this domain name to an OpenShift v3 web app. (It is my first time setting up things like this, so bear with my ignorance.) Normally, OpenShift provides a hostname, something like:
myapp-myproject.preview.openshiftapps.com
Based on conversation with support of my domain name registry company (not GoDaddy), I need to have some static IP from my Web Hosting provider to add to the DNS Entry or NameServer to link to my domain name (in my domain name account page). It looks like they don't have a clue that PaaS company like OpenShift don't provide a static IP for hosted Web applications.
What I did, is to get the above URL from OpenShift and add this DNS entry as CNAME type, which still didn't work.
Anyone here who has an idea, what I should get from OpenShift in order to tie my domain name and web app?
The CNAME approach should be used. You don't need a static IP address in that case but would use the FQDN of the OpenShift ingress point. You then also need to expose the service in OpenShift via your FQDN and not let it use the generated one.
If you are using the OpenShift V3 developer preview though, I believe use of custom domains is not enabled. The only way I know to have custom host name with the developer preview is to use a proxy service in front.
BTW, do note that the developer preview only provides you a time limited account. You should not use it for real web sites.
How to add our own domain? Do we need to setup any environment like Node?There is an automated domain generated but I want the web app to run my personal domain.
After you've configured the custom domain in Bluemix, you must map the custom domain to the Bluemix system domain on your registered DNS server:
Set up a 'CNAME' record for the custom domain name on your DNS server\domain host.
Map the custom domain name to the secure endpoint for the Bluemix region where your application is running. Use the following region endpoints to provide the URL route that is allocated to your organization in Bluemix:
US-SOUTH: secure.us-south.bluemix.net
EU-GB: secure.eu-gb.bluemix.net
AU-SYD: secure.au-syd.bluemix.net
more information here: https://console.ng.bluemix.net/docs/manageapps/secapps.html and here https://console.ng.bluemix.net/docs/manageapps/updapps.html
In the next several months we will be going live with a web app ('MyApp') that is being hosted on Azure. We have purchased the MyApp.com domain and our Azure domain name is MyApp.azurewebsites.net.
We do not want our users to ever see the azure domain name in any form. We want them to see www.MyApp.com or www.MyApp.com/Sales/ViewSale etc.
I think I know how to map www.MyApp.com to MyApp.azurewebsites.net based on this article. We won't be able to set this up for a while, so I'd like to know what the user will see in their browser URL when they go to www.MyApp.com. Will they see www.MyApp.com or MyApp.azurewebsites.net? And then what will they see as they navigate various pages in the app?
Your azure website needs to be at least at the 'shared' level. This is the first tier of 'paid' azure website hosting. You do this under website > scale.
app service plan pricing tier = shared.
then you would choose 'configure' and look for 'domains' and add your www.myapp.com domain.
Then you head out to your DNS manager and add a CNAME record that directs traffic from www.myapp.com to myapp.azurewebsites.com, OR you can lookup up the Virtual (public) IP of your azure website and update the A record in your DNS manager.
Either route, your visitors will see www.myapp.com/mypage, www.myapp.com/mypage2, etc.
Once you have the proper hosting level (the control panel will tell you, look for custom domains) and configuration, they can access it as www.myapp.com. You may need to provide your own SSL cert in order to configure it as well.
When it comes time to SSL, check out this post (Azure SSL Certificate) that I made regarding uploading of SSL certs in the control panel. It will save you a headache.
The article you linked appears to have solid information based upon my recent experiences. One thing to note: It has screen shots from the old configuration panel, so some things may look different in the new one.
I haven't found a way to hide the myapp.azurewebsites.com method to access a page, other than maybe doing a redirect inside your code. However, until you have your DNS setup it might be nice to see things working under that domain to start.
I have an site hosted on Azure that I am trying to point a domain from Google Domains to.
My current configuration is as follows:
Name Type Data
# A XXX.XXX.XXX.XXX
www CNAME history-podcasts.azurewebsites.net
awverify CNAME awverify.history-podcasts.com
I am following the instructions from here: Configuring a custom domain name for an Azure Website.
When I go to the Azure portal to Manage Domain and attempt to enter the url in DOMAIN NAMES, I get the following message:
A CNAME record pointing from history-podcasts.com to history-podcasts.azurewebsites.net was not found. Alternative record awverify.history-podcasts.com to awverify.history-podcasts.azurewebsites.net was not found either
When I go to the URL for the domain, I get the following message:
The website you have attempted to reach is not available in this Microsoft Azure Web Sites region. This could be due to one of several reasons:
The web site owner has registered a custom domain to point to the Microsoft Azure Web Site, but has not yet configured Azure to recognize it. Click here to read more.
When a site owner wants to use a custom domain with a Microsoft Azure Web Sites website, Azure needs to be configured to recognize the custom domain name, so that it can route the request to the appropriate server in the region. After registering the domain with a domain provider and configuring a DNS CNAME record to point to the site's Azurewebsites.net address (for example, contoso.azurewebsites.net), the website owner also needs to go to the Azure Portal and configure the site for the new domain. Click here to learn more about configuring the custom domains for a web site.
This is the same configuration settings I am currently using for several domains through Namecheap with Azure hosting and they work as intended.
EDIT:
To summarize, here are the steps you need to take:
1) Create CNAME record redirecting user from your domain to Azure specified domain using tools provided by your DNS hosting service
This step will ensure that when going to www.history-podcasts.com user will transparently be taken to history-podcasts.azurewebsites.net
Type: CNAME
Name: www
Value: history-podcasts.azurewebsites.net
IMPORTANT: Please note that it takes time for DNS servers to update their records therefore you should wait around 30 minutes before continuing.
2) Redirect your naked domain to subdomain using DNS hosting service tools
This step will ensure that when going to history-podcasts.com user will be redirected to www.history-podcasts.com
For Google Domains you can follow this guide here.
3) Add your domain to Azure Website
This step will assure Azure that you own the domain and you want your site to be reachable using specified domain name.
Login into https://manage.windowsazure.com/
Navigate Websites -> [Your Website] -> Configure
Scroll down to Domain names
Click Manage Domains (note that custom domains can only be used when in the Shared, Basic, or Standard modes)
Add your domain www.history-podcasts.com
At this point you should be able to reach your web site using both history-podcasts.com and www.history-podcasts.com domain names.
If your website requires HTTPS, you will have to take extra steps:
http://azure.microsoft.com/en-us/documentation/articles/web-sites-configure-ssl-certificate/