Here is what I want to do:
I have a bunch of client URLs like client1.some.com and during maintenance I am redirecting them using Traffic Manager to banner.some.com
At this point it fails to show them my banner because their host names are not in "Custom Domain" section
I want to find a way to use WebApp for all clients so it won't care from what URL it came from. In that case once I get more clients I don't have to go to my WebApp and add their host names.
By now I have to go to me DNS provider and add awverify records there only after that I am able to add new custom domain on web app.
I want to make IIS ignore host header info and just return index page from default web page.
Thanks
Ihor
Far as I know, if the client URLs you mentioned have the same root domain or subdomain (e.g. client1.some.com, client2.some.com or client1.a.some.com, client2.a.some.com), you could map a wildcard domain (e.g. *.some.com or *.a.some.com) to your Azure App, in order to meet your requirement. You could follow the steps below to achieve your purpose.
Create the DNS record(s)
Please log in to your domain registrar and use their tool to add A CNAME record.
Your CNAME record should be configured as follows:
| FQDN EXAMPLE | HOST/NAME/HOSTNAME | Value |
| ----------------------------- | ------------------ | -------------------------- |
| *.some.com (wildcard) | * | hostname of your Azure App |
| *.a.some.com (wildcard & sub) | * | hostname of your Azure App |
Please log in to the Azure portal, then configure the wildcard domain for your Azure App.
In addition, after you finish the configuration steps, it could take some time for the changes to take effort.
You could visit http://digwebinterface.com/ to check whether the DNS propagation is working as expected.
For more details, you could refer to this tutorial.
Related
Some of my apps are not working from some customers site, I later discovered that this was because I am using the default websites for my app hosting that is the url is myapp.azurewebsites.net which was not whitelisted on the customers firewall. The customer whitelisted my website domain name and its sub domain names .i.e mywebsite.com and *.mywebsite.com are all whitelisted.
If i were to create CNAME record which has a CNAME pointer to the azure default web app for example myapp.mywebsite.com points to myapp.azurewebsites.net, will this get around the issue ? Or do I need to whitelist myapp.azurewebsites.net Or its IP address that is the IP address of myapp.azurewebsites.net ?
Firstly, by default, apps hosted in App Service are accessible directly through the internet and can reach only internet-hosted endpoints. So, typically, anyone with the URL without any specific local network/firewall/proxy restrictions can access the WebApp URL.
As I understand, your WebApp is open to the public and only a few users (on a specific network), have trouble accessing the site. Plus, there are no access restrictions that you have implemented from the WebApp side.
Just to highlight,
Network administrators often deploy proxy servers, firewalls, or other
devices, which can help secure and give control over how users access
the internet. Rules designed to protect users can sometimes block or
slow down legitimate business-related internet traffic. This traffic
includes communications between you and Azure over the URLs listed
here.
Reference : Allow the Azure portal URLs on your firewall or proxy server
So, on case-case basis, for the affected network, you may have them add appservice.azure.com (Azure App Services) in the allowed list.
Or
As your customer performed – “The customer whitelisted my website domain name and its sub domain names .i.e mywebsite.com and *.mywebsite.com are all whitelisted.” have them add the URLs to allowedlist.
Or
Since IP address of your WebApp (see the reasons for the change), the best route would be for you to set up a custom domain for your WebApp.
Kindly check this doc - Tutorial: Map an existing custom DNS name to Azure App Service
The CNAME maps to the app's default hostname instead, which is less susceptible to change. | | Wildcard | *.contoso.com | CNAME record. |
-- As a side note (as indicated above), by setting up access restrictions, you can define a priority-ordered allow/deny list that controls network access to your app. Which is the opposite of your scenario, just sharing as FYI, in case you wish to know about access restrictions from WebApp side. Set up Azure App Service access restrictions
I have FrontDoor instance myFrontDoor configured with wildcard domain (single CNAME record on .myDomain.com directed to myFrontDoor.azurefd.net).
Setup of frontdoor looks like:
Domain | Backend pools | Rules
myFrontDoor.azurefd.net | backendPool-A | rule-A
*.myDomain.com | backendPool-B | rule-B
I would like to set up rules in a way that:
ruleA forwards all requests for a*.myDomain.com/* to backendPool-A (e.g. a1.myDomain.com, a2.myDomain.com)
ruleB forwards all requests for b*.myDomain.com/* to backendPool-B (e.g. b1.myDomain.com, b2.myDomain.com)
I tried to setup a pattern in a rule to be like
a*.myDomain.com/* but it says that:
Pattern is invalid, it must start with '/' (by Azure Portal)
I tried to do this by Azure CLI as well but error occurs as well.
According to Microsoft documentation for FrontDoor and wildcard domains it should work.
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'm a little lost here and would appreciate some help:
I've set up an app service that works with:
tenant1.myapp.com
tenant2.myapp.com
etc.
I wan't to make make custom domains to work for the tenants, so that
customtenantdomain.com can point to tenant2.myapp.com
The only way I've managed to get it to work is by manually adding a custom domain "customtenantdomain.com" in the azure portal, setup A and CNAME records and from there my code handles it based on the host name. I also need to set up
TXT myapp.azurewebsites.net awverify
Is it possible to do this in another way, or at least programatically?
Ideally, I would like to only point the A-record from the domain to point to the azure IP
A # 23.100.50.51
along with
TXT myapp.com awverify
But that does not work, obviously. Is there any reason why that should not work?
It is possible to set up mappings using powershell:
Get-AzureDeployment -ServiceName yourservicename | Select Url
Here is some more information:
https://learn.microsoft.com/en-us/azure/cloud-services/cloud-services-custom-domain-name
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