[Bug 1710666] Re: No resolution until manually adding a nameserver to resolv.conf

2017-08-21 Thread Dimitri John Ledkov 
I am very glad to hear this =)

That would be these changes:
  * Set UseDomains to true, by default, on Ubuntu.
On Ubuntu, fallback DNS servers are disabled, therefore we do not leak 
queries
to a preset 3rd party by default. In resolved, dnssec is also disabled by
default, as too much of the internet is broken and using Ubuntu users to 
debug
the internet is not very productive - most of the time the end-user cannot 
fix
or know how to notify the site owners about the dnssec mistakes. 
Inherintally
the DHCP acquired DNS servers are therefore trusted, and are free to spoof
records. Not trusting DNS search domains, in such scenario, provides limited
security or privacy benefits. From user point of view, this also appears to 
be
a regression from previous Ubuntu releases which do trust DHCP acquired 
search
domains by default.
Therefore we are enabling UseDomains by default on Ubuntu.
Users may override this setting in the .network files by specifying
[DHCP|IPv6AcceptRA] UseDomains=no|route options.
  * resolved: create private stub resolve file for integration with resolvconf.
The stub-resolve.conf file points at resolved stub resolver, but also lists 
the
available search domains. This is required to correctly resolve domains 
without
using resolve nss module.
  * Enable systemd-resolved by default
  * Create /etc/resolv.conf at postinst, pointing at the stub resolver.
The stub resolver file is dynamically managed by systemd-resolved. It 
points at
the stub resolver as the nameserver, however it also dynamically updates the
search stanza, thus non-nss dns tools work correctly with unqualified names 
and
correctly use the DHCP acquired search domains.
  * libnss-resolve: do not disable and stop systemd-resolved
resolved is always used by default on ubuntu via stub resolver, therefore it
should continue to operate without libnss-resolve module installed.

>From the 234-2ubuntu1, which only just migrated =) See:

https://launchpad.net/ubuntu/+source/systemd/+changelog

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710666

Title:
  No resolution until manually adding a nameserver to resolv.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710666/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1710666] Re: No resolution until manually adding a nameserver to resolv.conf

2017-08-21 Thread Shahar Or 
I don't know what changed it, but this time I booted, I don't have this
issue any more. Must have been something here:

```
Start-Date: 2017-08-20  11:27:27
Requested-By: shahar (1000)
Install: libtracker-sparql-2.0-0:amd64 (1.99.2-0ubuntu1, automatic), 
python3-newt:amd64 (0.52.18-3ubuntu3, automatic)
Upgrade: bluez:amd64 (5.45-0ubuntu4, 5.46-0ubuntu1), libqpdf17:amd64 (6.0.0-2, 
6.0.0-2ubuntu1), libefivar1:amd64 (30-1ubuntu1, 31-1), libpangoft2-1.0-0:amd64 
(1.40.6-1, 1.40.11-0ubuntu1), gnome-video-effects:amd64 (0.4.1-3ubuntu1, 
0.4.3-1ubuntu1), gir1.2-gtk-3.0:amd64 (3.22.17-0ubuntu1, 3.22.18-1ubuntu1), 
python-samba:amd64 (2:4.5.8+dfsg-2ubuntu5, 2:4.6.5+dfsg-8ubuntu1), 
libsasl2-modules-db:amd64 (2.1.27~101-g0780600+dfsg-2ubuntu1, 
2.1.27~101-g0780600+dfsg-3ubuntu1), xserver-common:amd64 (2:1.19.3-1ubuntu2, 
2:1.19.3-1ubuntu3), python3-software-properties:amd64 (0.96.24.14, 0.96.24.15), 
bluez-cups:amd64 (5.45-0ubuntu4, 5.46-0ubuntu1), xserver-xorg-core:amd64 
(2:1.19.3-1ubuntu2, 2:1.19.3-1ubuntu3), byobu:amd64 (5.118-0ubuntu1, 
5.122-0ubuntu1), libhd21:amd64 (21.46-1, 21.47-1), libwbclient0:amd64 
(2:4.5.8+dfsg-2ubuntu5, 2:4.6.5+dfsg-8ubuntu1), libsystemd0:amd64 
(233-8ubuntu3, 234-2ubuntu6), libgtk-3-common:amd64 (3.22.17-0ubuntu1, 
3.22.18-1ubuntu1), xdg-user-dirs:amd64 (0.15-2ubuntu7, 0
 .15-3ubuntu1), libgtk-3-0:amd64 (3.22.17-0ubuntu1, 3.22.18-1ubuntu1), 
keybase:amd64 (1.0.28-20170815161818.fed6e3db9, 
1.0.29-20170818161957.4d0259c85), snapd:amd64 (2.26.10+17.10, 2.27.3+17.10), 
libopenmpt0:amd64 (0.2.8461~beta26-1, 0.2.8760~beta27-1), libefiboot1:amd64 
(30-1ubuntu1, 31-1), ubuntu-standard:amd64 (1.394, 1.396), 
grilo-plugins-0.3-base:amd64 (0.3.4-2ubuntu3, 0.3.4-2ubuntu4), 
gir1.2-pango-1.0:amd64 (1.40.6-1, 1.40.11-0ubuntu1), udev:amd64 (233-8ubuntu3, 
234-2ubuntu6), libsasl2-2:amd64 (2.1.27~101-g0780600+dfsg-2ubuntu1, 
2.1.27~101-g0780600+dfsg-3ubuntu1), resolvconf:amd64 (1.79ubuntu6, 
1.79ubuntu7), software-properties-gtk:amd64 (0.96.24.14, 0.96.24.15), 
libudev1:amd64 (233-8ubuntu3, 234-2ubuntu6), hwinfo:amd64 (21.46-1, 21.47-1), 
libio-socket-ssl-perl:amd64 (2.049-1, 2.050-1), gir1.2-nautilus-3.0:amd64 
(1:3.24.2.1-0ubuntu1, 1:3.24.2.1-0ubuntu2), libapt-pkg-perl:amd64 
(0.1.32build1, 0.1.33), libgmime-3.0-0:amd64 (3.0.1-3, 3.0.1-4), 
samba-libs:amd64 (2:4.5.8+dfsg-2ubunt
 u5, 2:4.6.5+dfsg-8ubuntu1), xserver-xephyr:amd64 (2:1.19.3-1ubuntu2, 
2:1.19.3-1ubuntu3), libpangoxft-1.0-0:amd64 (1.40.6-1, 1.40.11-0ubuntu1), 
apport:amd64 (2.20.6-0ubuntu5, 2.20.6-0ubuntu6), libappstream-glib8:amd64 
(0.7.1-1, 0.7.1-2), nautilus:amd64 (1:3.24.2.1-0ubuntu1, 1:3.24.2.1-0ubuntu2), 
libnautilus-extension1a:amd64 (1:3.24.2.1-0ubuntu1, 1:3.24.2.1-0ubuntu2), 
libgtk-3-bin:amd64 (3.22.17-0ubuntu1, 3.22.18-1ubuntu1), libsasl2-modules:amd64 
(2.1.27~101-g0780600+dfsg-2ubuntu1, 2.1.27~101-g0780600+dfsg-3ubuntu1), 
libpangocairo-1.0-0:amd64 (1.40.6-1, 1.40.11-0ubuntu1), python3-apport:amd64 
(2.20.6-0ubuntu5, 2.20.6-0ubuntu6), samba-common:amd64 (2:4.5.8+dfsg-2ubuntu5, 
2:4.6.5+dfsg-8ubuntu1), systemd-sysv:amd64 (233-8ubuntu3, 234-2ubuntu6), 
libglib2.0-bin:amd64 (2.53.4-3, 2.53.4-3ubuntu1), ufw:amd64 (0.35-4, 0.35-5), 
libpam-systemd:amd64 (233-8ubuntu3, 234-2ubuntu6), libgail-3-0:amd64 
(3.22.17-0ubuntu1, 3.22.18-1ubuntu1), neovim:amd64 
(0.2.0ubuntu1+git201708161935+3603+26~ubuntu17.0
 4.1, 0.2.0ubuntu1+git201708191115+3605+26~ubuntu17.04.1), systemd:amd64 
(233-8ubuntu3, 234-2ubuntu6), libwebkit2gtk-4.0-37:amd64 (2.16.6-1, 
2.17.91-1ubuntu1), libsmbclient:amd64 (2:4.5.8+dfsg-2ubuntu5, 
2:4.6.5+dfsg-8ubuntu1), smbclient:amd64 (2:4.5.8+dfsg-2ubuntu5, 
2:4.6.5+dfsg-8ubuntu1), samba-common-bin:amd64 (2:4.5.8+dfsg-2ubuntu5, 
2:4.6.5+dfsg-8ubuntu1), qpdf:amd64 (6.0.0-2, 6.0.0-2ubuntu1), 
libgcab-1.0-0:amd64 (0.7-3, 0.7-4), libglib2.0-data:amd64 (2.53.4-3, 
2.53.4-3ubuntu1), apport-gtk:amd64 (2.20.6-0ubuntu5, 2.20.6-0ubuntu6), 
gir1.2-appstreamglib-1.0:amd64 (0.7.1-1, 0.7.1-2), nautilus-data:amd64 
(1:3.24.2.1-0ubuntu1, 1:3.24.2.1-0ubuntu2), libxres1:amd64 (2:1.0.7-1, 
2:1.0.7-2), gtk-update-icon-cache:amd64 (3.22.17-0ubuntu1, 3.22.18-1ubuntu1), 
cron:amd64 (3.0pl1-128ubuntu3, 3.0pl1-128ubuntu4), xvfb:amd64 
(2:1.19.3-1ubuntu2, 2:1.19.3-1ubuntu3), libbluetooth3:amd64 (5.45-0ubuntu4, 
5.46-0ubuntu1), libpango-1.0-0:amd64 (1.40.6-1, 1.40.11-0ubuntu1), 
poppler-data:amd64 (0.4.7-8, 0.4.
 8-1), libjavascriptcoregtk-4.0-18:amd64 (2.16.6-1, 2.17.91-1ubuntu1), 
python3-problem-report:amd64 (2.20.6-0ubuntu5, 2.20.6-0ubuntu6), 
libsamplerate0:amd64 (0.1.8-8, 0.1.9-1), libglib2.0-0:amd64 (2.53.4-3, 
2.53.4-3ubuntu1), libidn2-0:amd64 (2.0.2-1, 2.0.2-3), 
libwebkit2gtk-4.0-37-gtk2:amd64 (2.16.6-1, 2.17.91-1ubuntu1), 
libclutter-gtk-1.0-0:amd64 (1.8.2-2, 1.8.4-1), libtext-charwidth-perl:amd64 
(0.04-7build7, 0.04-7.1), software-properties-common:amd64 (0.96.24.14, 
0.96.24.15)
Purge: python3-distro-info:amd64 (0.17), update-manager-core:amd64 (1:17.10.5), 
ifupdown:amd64 (0.8.16ubuntu2), update-notifier-common:amd64 (3.183), 
bri

[Bug 1710666] Re: No resolution until manually adding a nameserver to resolv.conf

2017-08-17 Thread Mikhail N 
Post the output of
$ sudo systemctl status systemd-resolved

And try:
$ sudo systemctl restart systemd-networkd
Will DNs resolution start working after it?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710666

Title:
  No resolution until manually adding a nameserver to resolv.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710666/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1710666] Re: No resolution until manually adding a nameserver to resolv.conf

2017-08-17 Thread Mikhail N 
NetworkManager does not take care of DNS resolution, in Ubuntu 17.10
systemd-resolved does it, dnsmasq did it in older Ubuntu releases.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710666

Title:
  No resolution until manually adding a nameserver to resolv.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710666/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1710666] Re: No resolution until manually adding a nameserver to resolv.conf

2017-08-17 Thread Mikhail N 
Oh, sorry!
Not
$ sudo systemctl restart systemd-networkd


but
$ sudo systemctl restart systemd-resolved

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710666

Title:
  No resolution until manually adding a nameserver to resolv.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710666/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs