The estimated reading time for this post is 2 minutes
This post describes how I configured one of my Windows Azure hosted Virtual Machines with my domain name registrars DNS – this meant that I could make SharePoint 2013 available using my domain name.
On the virtual machine instances, page in the Windows Azure Management Portal (https://manage.windowsazure.com) browse to the virtual machine you want to configure with your external DNS.
On the right, in the “Quick Glance” section you will see that a “Public Virtual IP (VIP) Address” is listed (this is shown in the image below but for security purposes, I have changed my VIP to 220.127.116.11). The VIP address is the IP address I need to direct my external DNS to.
This VIP address is guaranteed to remain for the deployment of the cloud service – therefore if the deployment is removed the VIP address will no longer be available. Corey Sanders has written a great article on the Windows Azure MSDN blog (http://blogs.msdn.com/b/windowsazure/archive/2011/07/06/windows-azure-deployments-and-the-virtual-ip-address.aspx) where he confirms that the VIP is guaranteed for the lifetime of deployment and provides a great alternative if the virtual machine deployment has to be removed.
“If that is not possible (e.g. you must delete/deploy), then a little planning beforehand can still help here: just create a new hosted service, update CNAME and A record to new hosted service (but keep old deployment there). Wait 24 hours and it should be safe to delete the older deployment.”
I also decided to add a shorter TTL to my A record just in case the VIP address does ever change for whatever reason and I need to propagate a change quickly. I’m not sure if this is advisable or not and am seeking confirmation on this.
A quick test you can do before making any changes to your DNS is to browse directly to your VIP address (http://18.104.22.168). This in my case took me to the default IIS site however this will depend on your configuration.
After I confirmed that the VIP address was accessible I then proceeded to make changes to my external DNS through my domain registrars control panel – in this example, I wanted to point a host record (or an A record) to my virtual machine.
2 thoughts on “Pointing external DNS at a Windows Azure hosted Virtual Machine”
This article has been very useful – I experienced the same issue as you and have now switched to using a CNAME. It was also reassuring to confirm this using the links you provide.
Thanks Juff – glad you found it of use!