> In the past prior to systemd-resolve as a default solution the order I
> think was followed. From what I understand windows
> https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-
> server-2008-R2-and-2008/dd197552(v=ws.10)
> prefers first server on the list (it doesn't
>
> 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
On Wed, 11 Oct 2023 at 09:37, Marc wrote:
> Having 3 different nameservers reporting different results?
>
An example I have seen quite frequently is where there is an internal DNS
which resolves local (internal) server resources and forwards anything else
to an external server such as 8.8.8.8.
>
> I hope this is the right mailing list to ask that kind of question. I'm
> following what is recommended on github issue tracker:
> https://github.com/systemd/systemd/issues/new/choose
> If it's not - feel free to point me to a different place.
>
> I use azure ubuntu 20.04 build with
W dniu 2023-10-11 09:50, Marc napisał(a):
I think this is not how resolv.conf was designed to be used. Are you
100% sure this is the only way to solve your issue? Having 3 different
nameservers reporting different results? Can't you do something with
views and sorting? What about just giving
I hope this is the right mailing list to ask that kind of question. I'm
following what is recommended on github issue tracker:
https://github.com/systemd/systemd/issues/new/choose
If it's not - feel free to point me to a different place.
I use azure ubuntu 20.04 build with nameservers obtained
