I had troubles with DNS resolution in last days after reboot and I think it may be related to resolvconf package update. I spotted following entries in resolvconf-pull-resolved.service journal:
mar 14 09:30:01 *** systemd[1]: resolvconf-pull-resolved.service: Start request repeated too quickly.
mar 14 09:30:01 *** systemd[1]: resolvconf-pull-resolved.service: Failed with result 'start-limit-hit'.
mar 14 09:30:01 *** systemd[1]: Failed to start resolvconf-pull-resolved.service.
Because of that DNS resolution was not working after boot but I used workaround of disabling and enabling Wifi from GUI. I guess resolvconf-pull-resolved.service was started too many times right after booting the system.
For now I just uninstalled resolvconf package and it should fix it but I hope my message can help to track the problem.
I had troubles with DNS resolution in last days after reboot and I think it may be related to resolvconf package update. I spotted following entries in resolvconf- pull-resolved. service journal:
mar 14 09:30:01 *** systemd[1]: resolvconf- pull-resolved. service: Start request repeated too quickly. pull-resolved. service: Failed with result 'start-limit-hit'. pull-resolved. service.
mar 14 09:30:01 *** systemd[1]: resolvconf-
mar 14 09:30:01 *** systemd[1]: Failed to start resolvconf-
Because of that DNS resolution was not working after boot but I used workaround of disabling and enabling Wifi from GUI. I guess resolvconf- pull-resolved. service was started too many times right after booting the system.
For now I just uninstalled resolvconf package and it should fix it but I hope my message can help to track the problem.