When you publish an application to Windows Azure, it gets its own subdomain in cloudapp.net. In order to make name resolution even faster (particularly outside the USA), the Domain Name System (DNS) used by Azure is moving to a new globally distributed infrastructure. As the article mentions, there is no customer action required.
Similar Posts
SQL Azure Federations: Robust Connectivity Model for Federated Data
Another article on sharding SQL Azure Databases using Federation. Good tips on how to migrate to a multi-tenant model as well. Click here to open link…
Top Windows Azure Support Issues when upgrading to v1.3 of the SDK
Workarounds for resolving the two most common issues when upgrading to version 1.3 of the Windows Azure SDK. Click here to open link…
Node.js and Windows Azure bootcamp in Salt Lake City
I had a chance to talk – along with my friend and colleague Steve Seow – about Node.js and Windows Azure this past Saturday in beautiful Salt Lake City. We had a really enthusiastic audience, building Node.JS application from scratch and learning about the benefits of the Windows Azure PaaS model, which facilitates and simplifies…
WordPress.com and Windows Live partnering together
This is amazing news, particularly when one's blog is based on WordPress. 🙂 WordPress.com and Windows Live partnering together link
Automated Build and Deployment with Windows Azure SDK 1.6
Tom Hollander recently posted a great article on how to use the new deployment capabilities in the Windows Azure SDK v1.6, including the use of the .publishsettings file with a build server using TFS and MSBuild. Enjoy! Click here to open link…
Windows Azure SDK version 1.4 has been released
The Windows Azure team announced the release of version 1.4 for the Windows Azure SDK, along with the corresponding update to the management console. The official announcement can be found here: http://tinyurl.com/46cn8bc The SDK is now available on the Microsoft downloads website, found here: http://tinyurl.com/2c8r9a7 The following features have been added: