[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: systemd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I think I'll steer away from systemd-resolved
1) it does not favor my primary nameserver (after a switch it'll not switch
back, but continue any failover server)
2) in the end it can even use a nameserver which I have not provided (which is
set by the packagebuilder)
Reading into some threads
For completeness, 01-netcfg.yaml for machine kvm1804
** Attachment added: "network configuration for machine kvm1804"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890903/+attachment/5403427/+files/01-netcfg.yaml
--
You received this bug notification because you are a member of
192.168.178.1 was defined as secondary nameserver on kvm1804 within
01-netcfg.yaml (ubuntu 18.04).
The primary nameserver is just operating properly. I do not see any
reason why systemd-resolved would not target this primary nameserver,
let alone target something external to me at all.
In case
I've now got one instance with this condition again.
>From what I can see from the logs is that systemd-resolved started using some
>other DNS server:
First one in my network where I do not have control over (ipv4: 192.168.178.1 ,
somehow it turned up with this fairly correct address : my
To debug the systemd-resolved service, you can run
$ sudo systemctl edit systemd-resolved
and in the editor that is opened, add and save this content:
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
then restart systemd-resolved, or reboot. Then once the problem happens
again, check:
$
6 matches
Mail list logo
