I'm a developer trying to test a Lync 2013 integration and I'm using Azure VMs as my test lab.
I have set up a cloud service with two machines. The first machine is my domain controller. It's running Active Directory and DNS. This machine's name is "controller". My second machine is running Lync 2013 Server Standard Edition. This machine's name is "lync".
The Lync server is part of the domain I set up on my first machine. I followed the Lync server install guide to get to this point. This topology is the minimum required to run Lync Server 2013 standard edition.
My domain is called lynctest.local. In my DNS server, "controller", I changed the A records for "lync.lynctest.local" and "controller.lynctest.local" to point to theexternal IP address of the cloud service. I then set my workstation to use the cloudservice IP as my DNS and I can log into Lync and test my integration from my Workstation.
The problem is that this works great except that every few hours, the A records get changed back to theinternal IP address without any human intervention. The VMs are not being restarted as far as I can tell. I open them in RDP and my last session is still active.
Does anyone know what is doing this and how I can disable it?
Also, note that I tried just using CNAME records for "lync" and "controller" to point to my cloudapp.net domain but Lync didn't seem to like that.