@Shahar this is not a support forum, this bug is closed. Please stop
commenting / high-jacking this bug report, for your own support query.
If you have a new bug report, please open a new bug report. This bug is
no longer monitored.
--
You received this bug notification because you are a member o
Should a process `systemd-resolved` be running? I don't have it running
at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685900
Title:
On artful, no working dns after upgrading to systemd 233-
On 26 July 2017 at 10:18, Shahar Or wrote:
> I do not seem to have the /etc/init.d/systemd-resolved symlink at all.
> Is this normal?
>
Yes normal, Ubuntu only supports systemd as the init system, and
/etc/init & /etc/init.d are not in use for most services. And,
specifically, init.d scripts have
I do not seem to have the /etc/init.d/systemd-resolved symlink at all.
Is this normal?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685900
Title:
On artful, no working dns after upgrading to syste
Here is my sosreport.
** Attachment added: "sosreport-ShaharOr.1685900-20170726121953.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1685900/+attachment/4921567/+files/sosreport-ShaharOr.1685900-20170726121953.tar.xz
--
You received this bug notification because you are a mem
I have a similar issue:
```
➜ ~ git:(master) ✗ systemd-resolve --status
Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.
```
```
➜ ~ git:(master) ✗ dpkg -l | grep systemd
ii dbus-user-session 1.10.18-1ubuntu2
This bug report is being closed due to your last comment regarding this
being fixed. For future reference you can manage the status of your own
bugs by clicking on the current status in the yellow line and then
choosing a new status in the revealed drop down box. You can learn more
about bug status
Just to be clear and let those interested know,
my setup is working fine now with the latest systemd (in proposed now)
233-5ubuntu1.
I installed and reinstalled several packages related to systemd and the command
"systemd-resolve --status"
is OK now.
Systemd-resolved is working well now.
So this
Dimitri,
I have a question about the chosen nameservers.
When using systemd 232-21-ubuntu3 or earlier, it was like this (systemd-resolve
--status):
Link 2 (eth0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC
** Description changed:
- After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got
no network.
+ After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got
no nameserver (dns).
This is very likely a DNS issue.
As a workaround downgrading back to system
Sosreport of my setup.
** Attachment added: "Sosreport"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1685900/+attachment/4868196/+files/sosreport-HarryKaasinen.systemd-20170426130934.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Dimitri,
Just added a sosreport as you requested.
My setup is a nearly minimal setup, containing only the applications I
need.
The issue here is what packages are needed to get the new systemd 233-5ubuntu1
and its resolved working.
And more, exactly those packages that were not needed to get sy
On 26 April 2017 at 09:11, Harry <1685...@bugs.launchpad.net> wrote:
> Dimitri,
>
> My setup does not need the package bind9.
> But I need to start systemd-resolved service manually.
>
> So, what do I have to do to get this working automatically at the boot?
>
Artful is not ready for general usage
Dimitri,
My setup does not need the package bind9.
But I need to start systemd-resolved service manually.
After that the output of systemd-resolve --status is OK:
Global
DNS Servers: 8.8.8.8
8.8.4.4
2001:4860:4860::
20
Dimitri,
one more test I just did.
I started systemd-resolved manually:
~$ sudo service systemd-resolved restart
After that the output of systemd-resolve --status is OK:
Global
DNS Servers: 8.8.8.8
8.8.4.4
2001:4860:4860::
Dimitri,
thank you for the information.
Now, as I am not very familiar with the systemd nor the dns setup, I
would be happy if you could give me advice how to proceed on this issue.
The status of my setup is as follows.
I have installed all the latest packages of artful aardvark, also from propos
How does that service changed between these versions?
$ git diff v232..v233 src/resolve/ | diffstat
36 files changed, 950 insertions(+), 284 deletions(-)
And that's just resolved specific code, but there are a lot more changes
in shared code.
You have not provided any system logs, error messages
dnsutils with bind9-host should be sufficient on regular systems to have
network up.
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685900
Title:
On artful, no worki
OK,
So I got this issue fixed by installing the package bind9.
I tested several times, but dnsutils with bind9-host was not enough.
So I removed those two and installed bind9 instead.
Now I have a working dns.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Dmitri,
"I would like to see package versions of everything that is installed"
I have a fully updated artful setup with proposed enabled.
"... as per your messages it appears that systemd-resolved.service is not
running at all, when it should be."
Systemd-resolved.service works just fine with
Note i cannot reproduce your issue locally at the moment, and dns
resolution works for me as expected.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
I would like to see package versions of everything that is installed;
syslog and journal log; as per your messages it appears that systemd-
resolved.service is not running at all, when it should be.
Note that DNSSEC is re-enabled in artful.
--
You received this bug notification because you are a
22 matches
Mail list logo
