DC network location, when gateway is VM on same box

I know the dos and don'ts of domain controllers, and my setup is most certainly ill advised, but when ruing this kind of setup from home, on the cheap, I have little choice.

I have one physical machine, that hosts Hyper-V virtual machines. The physical box also acts as a domain controller, and one of the VMs is a pfSense gateway for firewall and natting.

When the machine starts up, the VM has not started, and as such the DC caot tell what network location it has so defaults to public.

This causes me some initial problems because of the firewall. While the machine is never going to leave this physical LAN, I would rather keep the domain network profile active. A simple powershell command to restart the adapter cures the issue.

Is there anyway to overcome this? The way I see it, I suspect I would have to move the pfSense gateway onto another machine so it is always up, that way the DC can contact it as soon as it starts up. Perhaps the network adapter could have a delayed start, or maybe a task to run sometime after startup to simply restart the adapter?

I guess the hyper-v service starts after the networking services, as otherwise the VMs have no networking on startup.