On Wed, Apr 13, 2016 at 04:43:27PM +0300, Ran Benita wrote:
> On Wed, Apr 13, 2016 at 01:04:17PM +, Zbigniew Jędrzejewski-Szmek wrote:
> > On Wed, Apr 13, 2016 at 02:26:49PM +0300, Ran Benita wrote:
> > > coredumpctl doesn't show the crash so can't say what it's about. Maybe
> > > it's a
On Wed, Apr 13, 2016 at 01:04:17PM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Wed, Apr 13, 2016 at 02:26:49PM +0300, Ran Benita wrote:
> > coredumpctl doesn't show the crash so can't say what it's about. Maybe
> > it's a distro problem (archlinux) or it's fixed in git.
>
> It's probably the
On Wed, Apr 13, 2016 at 02:26:49PM +0300, Ran Benita wrote:
> OK, I just looked at the logs and figured out what happens: resolved
> crashes whenever I perform a query with allow-downgrade, and after a few
> times it doesn't restart and presumably the nss module falls back to
> direct DNS queries.
OK, I just looked at the logs and figured out what happens: resolved
crashes whenever I perform a query with allow-downgrade, and after a few
times it doesn't restart and presumably the nss module falls back to
direct DNS queries. Here is the log:
Apr 13 13:56:31 ran systemd[1]: Started Network
Hey,
I read in the v229 NEWS that it is now possible to specify
DNSSEC=allow-downgrade and decided to try it. Note that I use my local
home router's DNS server which certainly does not support DNSSEC. I
configured the system to use resolved by changing "dns" to "resolve" in
nsswitch.conf. I use
