Dynamics Community Forum Thread Details

LCS Deployed High Availability Domain Controller -- Cannot change hard coded DNS!

I just recently deployed a High Availability (HA) AX environment from LCS. Once it was deployed, we realized that the address space we chose for the VNET would not work for us. I then changed all the static IPs to a new address space and deleted the old address space for the VNET. I also updated the DNS server for the VNET to reflect the new IP address of my first domain controller and figure out how to change the internal load balancer to reflect the new IPs.

Now for the problem -- Azure specifically says to NOT hard code IPs or DNS. It basically issues them through a DHCP type process and the DNS entries for the servers get pulled from what is set for the DNS servers for the VNET in the portal. This is TRUE for all server EXCEPT the 3 domain controllers that LCS deployed. They maintain the old IP entries for their old static IPs. This is reeking havoc now. Does anyone know how Azure or LCS is accomplishing this hard coded DNS configuration? How do I change it??? I am hoping it is a simple Azure powershell script or something like that. I am wondering if deleting the VM out of the portal, keeping the disks, then recreating the VM with the old disks would remove anything that might have been configured in Azure that is causing this?

Any help would be extremely appreciated. This client is trying to go live this weekend!

UPDATE: After dozens of hours messing around with it and within about an hour of putting this up on the forum, my friendly neighborhood Azure engineer called me. He had me run a SysInternals "Autoruns" that tells you everything that runs or starts when the server boots up. Turns out LCS has the server run a task scheduler process (in task scheduler under Microsoft / Windows / Powershell / Sheduled Jobs every time the server starts (and also every hour it looks like). I then went to the C:\Users\axlocaladmin.DOMAIN\AppData\Local\Microsoft\Windows\PowerShell\ScheduledJobs\ActiveDirectory_Dns_Override and edited the XML file that contains the variables for the PowerShell script to reflect the new IP addresses for DNS. Then I just ran the scheduled job and VIOLA.. Done.

Quick Links