There is no systemd in Docker Desktop where the docker daemon is running. The fact that you are using Windows, is not relevant here, since Docker is still running in the Linux virtual machine. Since there is no systemd there, no systemd-specific options will work.
I don’t see any DNS-related error. Can you quote the one line that you mean?
I am not even sure how DNS would be relevant when you are using an IP address.
It still seems like you start Docker Desktop before logging in to your account. Cany ou confirm that?
Docker Desktop is for development. People still want to start it without interactively logging in, but it is not an officially supported use case as far as I know.
If you want to start Docker Desktop right after starting Windows, you will probably need to implement your own way to delay starting Docker Desktop.
If you are starting Docker Desktop when you logged in, you can report the connection issue on GitHub