Would a low TTL on Windows DNS SOA record cause Windows to hang on bootup?

TL;DR at the bottom, this needs some background to make sense.

Troubleshooting a very strange problem here that has been going on for a couple of weeks now. It requires a laptop swap for those affected and I'm really struggling to find a definitive cause and fix it. It feels like a networking issue but I can't say what for sure.

A bit of preamble:

We're running Macbook Airs with native Windows 10 (mix of 1903/1909) and when they're away from the business network during this Covid-19 work from home period, a cold boot hangs either just before the login screen, or just after. The machine is responsive but never finishes what it's doing- like it's waiting for a timeout or something to complete which never does.

Forcing it into Safe Mode shows "a timeout occurred (30000 milliseconds) was reached while waiting for a transaction response from the DNSCache service" multiple times and no other clues. You can log in fine in Safe Mode- with or without networking.

Our software loadout is very minimal- Office 2016, Teams, LAPS, Synergist (billing/invoicing software, fairly basic but up to date) and OpenVPN.

I've sent out 6 laptops with a completely fresh install of 1909 with the default Apple-provided Bootcamp drivers to try and eliminate driver updates or OS issues - no change.

However I've just noticed that the SOA record for our internal domain name on our DNS server is set to 1 minute when it should be 1 hour- not sure why.

Does anyone have any experience of this problem and is there any way this very low TTL could be causing this issue when the laptops are away from our business network?

Is there any way to properly diagnose this?

TL;DR - 1 minute TTL on internal domain SOA record. Windows hanging on login when booting away from company network, DNSCache service referenced in Event Viewer. Having to swap laptops during lockdown, need help.