[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.
https://bu
On Tue, Apr 03, 2018 at 08:59:19AM -, Dimitri John Ledkov wrote:
> 1) one should not manually adjust search domains in /etc/resolv.conf
> 2) systemd-resolved should learn about search domains
> - for example, set search domains in /etc/systemd/resolved.conf if
> nothing sets them on per link b
1) one should not manually adjust search domains in /etc/resolv.conf
2) systemd-resolved should learn about search domains
- for example, set search domains in /etc/systemd/resolved.conf if
nothing sets them on per link basis vai resolved dbus api or
networkd.network files.
3) /etc/resolv.conf s
** Changed in: systemd (Ubuntu)
Status: Expired => Won't Fix
** Changed in: systemd (Ubuntu)
Status: Won't Fix => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net
[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.
https://bu
Note: the problem is now even worse than what I reported above. If I put
"search kamens.us" in /etc/resolv.conf and then try to resolve "jik5",
"jik5.kamens.us", or "jik5.kamens.us.", all of which should resolve
successfully, they all fail with SERVFAIL.
--
You received this bug notification beca
I haven't changed /etc/systemd/resolved.conf.
Here's systemd-resolve --status
Global
DNS Domain: cnn.com
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
Yes, systemd-resolved will still be in use as the local stub resolver.
But there have certainly been behavior differences between the stub
resolver and the dbus service in the past, so this was still useful to
rule out.
The problem is still not reproducible for me locally, however.
--
You receiv
I believe systemd-resolved is still active on the system. It's just not
queried over whatever interface nss_resolved uses, but over DNS, via the
stub resolver at 127.0.0.53. If the systemd-resolved has bad data, it
will probably return bad data on the DNS interface as well.
--
You received this
On Sat, Jan 27, 2018 at 01:55:07PM -, Jonathan Kamens wrote:
> I uninstalled libnss-resolve and the problem persists:
>
> $ sudo apt-get remove libnss-resolve
> ...
> $ sudo systemd-resolve --flush-caches
> $ host jik5
> Host jik5.quantopian.com not found: 2(SERVFAIL)
> $ cat /etc/resolv.conf
I uninstalled libnss-resolve and the problem persists:
$ sudo apt-get remove libnss-resolve
...
$ sudo systemd-resolve --flush-caches
$ host jik5
Host jik5.quantopian.com not found: 2(SERVFAIL)
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#
As of Ubuntu 17.10, libnss-resolve is not installed by default. Is this
problem reproducible when libnss-resolve is removed, using the resolved
stub resolver instead of the NSS module?
I don't appear to be able to confirm the original behavior against the
quantopian.com domain (I don't get any NS
** Package changed: glibc (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1717015
Title:
libc resolver stops searching domain search list after
13 matches
Mail list logo
