I have five AWS servers on a public subnet of a single VPC, each with its own elastic IP address. The subnet is 10.0.0.0/24. One server is a Win2016 domain controller. The remaining four are Win2016 members of that domain.
I'd like to reorganize things a bit, placing a number of the servers on a newly created private subnet, providing them outbound Internet access through a NAT Gateway. The new subnet will be 10.0.1.0/24.
Both subnets live in the same VPC in the same availability zone (Northern California).
One of the servers I plan to move to the private subnet will be the domain controller. The domain controller will naturally have a new IP address when it's restarted in the new subnet. My questions are:
How will the member servers know the new IP address of the domain controller? Is it simply a matter of changing their manual DNS entry to point to the address of the new domain controller or is there more to it than that? Note that neither the name of domain nor the domain controller's name is changing. I'm only moving the domain controller to a newly created subnet in the same VPC, so although the DC's IP will change due to being on a new subnet, everything else remains the same.
Are there configuration changes on the domain controller itself that I'll need to make? In researching this, I ran across some scenarios (not quite like mine) where the domain controller's 'Sites and Services' app needed to be tweaked to inform the DC of new subnets associated with the 'site.' Would this apply to me given that I only have one physical site?