Virtual domain controller loses domain connection after reboot

I have been seeing an issue where a 2019 virtual domain controller will restart and set its network type to Private instead of Domain.  This seems to be due to the virtual server starting up so quickly and causes issues with various computers and programs connecting to the server. 

If I restart the Network Location Awareness service the network interface immediately recognizes the connection to the domain and clients are able to connect. 

I have been adding the Netlogon service and as a dependancy to the NLA service as follows:

 - On the DC launch a command prompt with elevated privilages

 - run the command: sc config nlasvc depend= NSI/RpcSs/TcpIp/Dhcp/EventLog/NetLogon/DNS/NetTimeSvc

This will add the Netlogon and DNS services as dependancies and should delay the startup of the NLA service long enough to correctly identify the network connection as domain.