Port 53 Binding Failed on NextDNS Client Start (Windows)

Hi there, 

I have been trying to deploy the NextDNS client at an enterprise level and have run into a structural issue (However this might just be a me problem)

I have noticed that the client sets the endpoints DNS server to 127.0.0.1 for localhost redirection to the NextDNS client which is correct, however after a machine restart I get an application error from the NextDNS Client (and when manually trying to start the NextDNS service): 

Startup failed: proxy: udp: read udp 127.0.0.1:53: wsarecvmsg: The system detected an invalid pointer address in attempting to use a pointer argument in a call.

This points to port 53 already being used and DNS resolution will obviously fail as the service cannot start. On my machine port 53 is being consumed by svchost.exe.

I'd like to ask if this is standard behaviour and if so, which compromises need to be made for choosing the NextDNS client on endpoints? Also is this suitable for enterprise deployments?