I have a domain on Azure subscription A (www and no www). Our client added the proper awverify cnames and everything has worked great for the last few months. Now, I need to move them to a separate Azure subscription. I migrated the site to the new subscription (the current site is still live on the original subscription). I'm trying to determine the best way to switch the domains. The IP of the azure website is actually the same (for both subscriptions), but I am timid about switching the awverify cnames in order to add the domain to the new site. I don't want any downtime.
What's the best strategy?
Suggestion: ask support to move the web site (and any other associated assets - storage acct, database) from the current account to the new account. I'm not sure they can, but if they can, that may be simplest and least risky since the site itself would not change or need to experience any downtime.
It turned out that we had to remove the domain names from the original site and add them to the new site. This wasn't ideal, but it worked. It would be nice to be alerted by Azure that the domains wouldn't work on the new subscription site until removed from the old. Having support migrate the site would work, but didn't give me warm fuzzies that the Orchard CMS would remain intact through the process.
Related
I have a VM in Azure with IIS running and hosting a website. This site was originally written and hosted by another company and they recently moved it to this VM for us. The binding still shows as the old website name (as hosted on the other company's site) and we still access it by going to the original website URL name in our browser. The developer mentioned to me that I'd need to eventually change the binding to reflect something hosted by my company.
My question is what is my next step? I know how to change the binding, but I'm having trouble knowing what to change it to? Ideally, I'd like to have the site hosted in Azure - the url name does not matter to me, as long as I can change it from the old original one. I created a new Web App in Azure and am trying to point the website to that new url but it's not working. Not sure that's the best route anyway.
If I understood your question correctly, Original website may have a domain name associated with it. You will have to update the DNS records with PIP (static-public IP) of Azure VM (site is now running on IIS on Azure VM).
Trust this helps.
Right now to create a custom domain you have to setup a cname for verification, and then you have to setup your real record, and then you can finally after that go and add it to the site.
I'm doing this scripted with C# and that's tedious considering that we're hosting our DNS with Azure. I would have thought that I could have added an a record to Azure and then add it directly to the website automatically but I can't figure out how to do this.
Anyone have any suggestions on how I can skip the whole Cname creation stuff?
Thanks!
Did you purchase a custom domain through Azure Web Apps?
https://azure.microsoft.com/en-us/documentation/articles/custom-dns-web-site-buydomains-web-app/
If you did, then everything should get automatically setup properly.
If you didn't, then you'll need to do the work to set it all up yourself.
I've read all about configuring custom domains for Azure Websites and can't figure out what I'm doing wrong. I have many other custom domains setup within this same GoDaddy account pointing at this same Azure Website and working perfectly. I've done side-by-side comparisons of their A Records and CName Records and they look the same to me. What am I missing?
I've tried waiting for 6 hours or so for things to expire and take effect, but no difference. My other domains activated within 10min or so, so I don't think that's the problem.
Azure error next to the correct CNames in GoDaddy: https://db.tt/jx6aKzUQ
Here's a side-by-side of one which works (PortsHap.com) and the one which doesn't (LESHap.com). What am I missing?!
GoDaddy side-by-side: https://db.tt/1ZOclKU9
I did a DNS look-up of the CNames and they're being found properly: https://db.tt/wEarl1WW
I'm at a loss...
UPDATE:
I can't afford to be blocked by this any longer, so I just set up a different domain "LESHaps.com" and used it instead. I set it up with the same process, same settings, but now it works. It's utterly bizarre. This really seems like a bug in Azure Websites. If anyone has any thoughts on this, then I would love to hear them. I'll switch back to the on-brand domain if I find a way.
Have you previously had that domain associated with a different Azure website? I've found that you can't associate a domain with more than one Azure website, and you have to remove it from the first website before associating this with a second.
This could be a real problem if you purchased a domain which had previously belonged to someone else, because you'd have no way of getting them to unassociate the domain, thus you couldn't use it in azure even if you own it!
I have some HTML widgets hosted on an Azure website. I would like to move these to a different Azure website.
Unfortunately, the mobile apps that consume these widgets are referencing their Azure sub-domain name directly. Example: old_widgets_site.cloudapp.net
Now I would like to shut down the old location where the widgets are hosted and move over to a new Azure website. Example: new_widgets_site.cloudapp.net :)
Is there a way for me to shut down the old website while still supporting the older mobile apps? Or do I have to keep the old app alive so I can host some kind of URL redirect mechanism on it?
PS - I know it's much better to reference a "virtual" domain name and have that redirect to Azure using DNS CNAMEs and I will. My question is not about that, but about redirecting *.cloudapp.net sub-domains.
To my understanding there is no option within Azure Web Sites to configure a redirect from within the portal.
What you could do is keep the old Web Site active and replace the content with a URL redirect statement in the web.config file (See: http://www.iis.net/learn/extensions/url-rewrite-module/using-the-url-rewrite-module). Of course that does mean you need to keep the old Web Site active.
Maybe you want to submit this idea using the Azure Feedback Forums: http://feedback.azure.com/
I have a SharePoint virtual machine in one active directory domain (for example domain1) and I want to transfer all the sites it has to another active directory domain (domain2).
I don’t know which could be the best procedure to do this, if I detach and attach my virtual machine from domain1 to domain2 it probably didn’t work since all the accounts used by SharePoint are no longer valid. (Both domain are not in the same network and didn’t trust each other).
Additionally I could export the sites in domain1 and import them on domain2 using stsadm, but if I use this technique I have to manually install all the features, solutions and personalization I made on my original server.
Does anybody know the best approach to “move” the sites from one domain to another?
There is a STSADM Custom Extension: move web that should be what you are looking for:
C:>stsadm -help gl-moveweb
stsadm -o gl-moveweb
Moves a web.
Parameters:
-url
-parenturl
[-haltonwarning (only considered if moving to a new site collection)]
[-haltonfatalerror (only considered if moving to a new site collection)]
[-includeusersecurity (only considered if moving to a new site collection)]
[-retainobjectidentity (only considered if moving to a new site collection)]
You may have some sucess by adding a local account to the administrators group and joining the server to the new domain. Then manualy updateing all of the AD accounts that are used in the server. I sould note that all of your users will then have new accounts that are not related to the old ones.
You sould ask your domain admins about an SID update to the new accounts so they also have the SID's from the old domain.