> > Obviously there are other solutions to the problem described above (eg > having multiple internal servers, although my experience was in the SOHO > environment where that would be excessive). If as Rafał says Windows > prioritises the first DNS option then I'm pretty sure that wasn't always > the case, but it's been well over a decade since I got out of Windows IT > support! For now I would think of disabling systemd resolving (uninstall systemd-resolved) and maybe networkmanager, so you can have the resolv.conf back. I can also think of maybe doing something with dnsmasq, it is quite simple and maybe offers this.