Am Tue, 9 May 2017 20:37:16 +0200
schrieb Lennart Poettering :
> On Tue, 09.05.17 00:42, Kai Krakow (hurikha...@gmail.com) wrote:
>
> > Am Sat, 6 May 2017 14:22:21 +0200
> > schrieb Kai Krakow :
> >
> > > Am Fri, 5 May 2017 20:18:41 +0200
> > >
On Tue, 09.05.17 00:42, Kai Krakow (hurikha...@gmail.com) wrote:
> Am Sat, 6 May 2017 14:22:21 +0200
> schrieb Kai Krakow :
>
> > Am Fri, 5 May 2017 20:18:41 +0200
> > schrieb Lennart Poettering :
> >
> > > On Fri, 05.05.17 01:01, Kai Krakow
Am Sat, 6 May 2017 14:22:21 +0200
schrieb Kai Krakow :
> Am Fri, 5 May 2017 20:18:41 +0200
> schrieb Lennart Poettering :
>
> > On Fri, 05.05.17 01:01, Kai Krakow (hurikha...@gmail.com) wrote:
> >
> > > Hello!
> > >
> > > Why is systemd-resolved
Am Fri, 5 May 2017 20:18:41 +0200
schrieb Lennart Poettering :
> On Fri, 05.05.17 01:01, Kai Krakow (hurikha...@gmail.com) wrote:
>
> > Hello!
> >
> > Why is systemd-resolved switching DNS servers all day long? This
> > doesn't seem to be right...
>
> If you turn on
On Fri, 05.05.17 01:01, Kai Krakow (hurikha...@gmail.com) wrote:
> Hello!
>
> Why is systemd-resolved switching DNS servers all day long? This
> doesn't seem to be right...
If you turn on debug logging, you should see an explanation right
before each switch. I figure we should choose the log
Hello!
Why is systemd-resolved switching DNS servers all day long? This
doesn't seem to be right...
Mai 05 00:52:46 jupiter systemd-resolved[658]: Switching to DNS server
192.168.4.254 for interface enp5s0. Mai 05 00:52:53 jupiter
systemd-resolved[658]: Switching to DNS server