Garry Shape
asked on
Adding VM Domain Controller in Azure to on-prem Domain - manual DNS settings?
I have an Azure VPN established to my on-prem firewall where my single domain AD Forest is. My goal is to get a Domain Controller VM up and running in Azure. I can already connect to the VM from on-site and vice versa, but I haevn't promoted to a DC yet.
My question is, would I need to configure the DNS settings at the VM level to point to an on-prem DC for it to see and join the domain? It's a single VNet with multiple subnets so I don't want the whole VNet using an on-prem DC as DNS.
I was going to also setup Windows Virtual Desktop in Azure and I'm not sure if those VMs that join this Domain would need to be using it as a DNS server or not.
And should I set the Azure VM DC to a static IP in its NIC properties?
My question is, would I need to configure the DNS settings at the VM level to point to an on-prem DC for it to see and join the domain? It's a single VNet with multiple subnets so I don't want the whole VNet using an on-prem DC as DNS.
I was going to also setup Windows Virtual Desktop in Azure and I'm not sure if those VMs that join this Domain would need to be using it as a DNS server or not.
And should I set the Azure VM DC to a static IP in its NIC properties?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Seperate vnet with the Azure DC VM set as DNS server for that vnet.