Another systemd-resolved problem in 17.04

[Chris Green]

On Wed, Jun 21, 2017 at 12:09:02PM -0400, Tom H wrote:
> On Wed, Jun 21, 2017 at 7:19 AM, Chris Green <cl at isbd.net> wrote:
> > On Wed, Jun 21, 2017 at 06:35:13AM -0400, Tom H wrote:
> >> On Wed, Jun 21, 2017 at 5:04 AM, Chris Green <cl at isbd.net> wrote:
> >>>
> >>> After my problems with systemd-resolved being unable to resolve
> >>> unqualified names I've hit another issue that seems to be a
> >>> resolver problem as well.
> >>>
> >>> I left my laptop running for a few days and this morning DNS was
> >>> broken, most queries were getting REFUSED returned by the local
> >>> resolver. All other systems on the LAN (not yet 17.04) had DNS
> >>> functioning OK.
> >>>
> >>> Restarting system-resolved seems to have fixed the problem (I did
> >>> mean to send it a SIGUSR2 but killed it by mistake).
> >>
> >> Without the relevant logs, no one'll be able to help you - here or in
> >> a bug report.
> >
> > So what/where are 'the relevant logs', the system hasn't been
> > restarted.
> 
> All syslog managers log more than just boot messages!
> 
> For RELEVANT messages, you could start with "journalctl -u
> systemd-resolved.service".
> 
I looked in syslog and there's nothing very significant there.

... and:-

    root at t470:~# journalctl -u systemd-resolvd.service
    -- No entries --
    root at t470:~# 

I also grepped through the files in /var/log and didn't find anything
very useful.


-- 
Chris Green

-- 
ubuntu-users mailing list
ubuntu-users at lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users