All geek questions in one place

How to configure custom domains in SAAS (Windows Azure)?

We are building a SAAS solution on Windows Azure. Each client should be able to map their own domain (example.com) with our service.

According to this article, there are two options for mapping a custom domain to a hosted Azure service:

  • CNAME record (subdomain required, e.g. www). This is not the case. An option without a subdomain should have.

  • Map entry A to VIP (virtual IP). It is better. It is mentioned that: "The VIP version of the deployment is not guaranteed to be changed unless the deployment for the hosted service is deleted." But a few days ago, our IP address suddenly changed without deleting. This is currently a trial account (90 days) and only one instance is used. This may be the cause.

At first, we planned to map user domains (example.com, etc.) to VIP using record A, but it seems to be unstable. At least in court this is not so.

Has anyone built something similar? How to perform stable mapping for user domains?

+4
source share
2 answers

I will go with CNAME because this is what has been widely used by Windows Azure users around the world, however, as a guarantee of Windows Azure that the VIP will not change during the life of the service until you delete the service, so you can use it. I saw how users started using it as well.

-> About your claim that the VIP has changed, even if you did not delete your service, I would say that this should not even be with a trial account.

  • How did you deploy your application? If you deploy the application in such a way that the previous deployment is removed and the new deployment, this can lead to a change in VIP. For example, deploying from VS, delete the existing deployment and then create a new one which will lead to the same behavior. It is always good to upgrade an existing deployment and make sure that the process you are using is updating (without deleting + a new deployment).

If your case was not above, and you are sure that your VIP has been changed without deleting the existing deployment, you should notify Windows Azure Support, as Windows Azure declares that the VIP will not change during the service life if it is not deleted.

+1
source

The best way to handle this is with option 1 above. Your service may decline for a number of reasons, and all this does not guarantee that the VIP will remain unchanged. Thus, the safest way would be to use CNAME.

0
source

Source: https://habr.com/ru/post/1411524/

More articles:


All Articles