I'm sorry @hrvooje - it worked for me.
But I have now risked upgrading my main laptop from 16.10 to 17.04 and it
appears to be working perfectly without the necessity for tweaks or
workaronds or alternative of 8.8.8.8 , etc, etc. I guess the latest in-situ
upgrade contained its own bugfix.
David
O
OK - complete solution/workaround is to be found here... But you must read
the whole lot before doing anything at all because the last edit makes the
first part redundant...
http://www.hecticgeek.com/2017/04/ubuntu-17-04-systemd-dns-issues/
The issue involves systemd within which the developers hav
For me:
work-wire OK
work-wifi OK
home-wifi FAIL
I don't use a wire at home so I didn't try
Then I do sudo service network-manager restart and I can surf again. In
that time while I can't sufr the internet I get ping 8.8.8.8 and other
IP's. Torrent dowloading is also working in that time. So, this
Temporary workaround which seems to work most of the time (though,
'timing' - as you are suggesting - sometimes is an issue, requiring a
couple of 'sudo apt update' attempts in Terminal to successfully resolve
all repositories) enter 8.8.8.8 (Google's DNS) into the relevant
'alternate DNS' in I
On second thoughts, despite 'dnsutils' and 'bind9-host' updates 17.04 is
still buggy on my two Toshiba laptops (one ancient, one less so). Can take
up to three attempts to resolve all repositories with 'sudo apt update'
after boot. Alternatively, on first attempts, browsers (Firefox, Chromium)
do n
Fortunately I had retained 17.04 full installation on a USB stick.
Downloaded new update via Google DNS on IPV4, then deleted 8.8.8.8 and
tested. Seems to be working. So far so good Thanks for the heads-up
hrvooje!
Best
David
On 18 April 2017 at 07:09, hrvooje <1654...@bugs.launchpad.net> wrot
Yup... Me, I'm reverting back to 16.10
D
On 17 Apr 2017 15:51, "harry brijs" wrote:
> i installed from iso file
> internet is avail upon goodwill of the system
> or whatever.
> It comes but most of the time it does not stay.
> I did not yet correlate this behaviour
> 2
>
> --
> You received this
Actually there seem to be two related or unrelated issues. One seems to be
purely DNS and the other Network Manager... Dunno. My original issue was
Network Manager. Now ok for no reason i can see. The more sticky one with
my latest upgrade was no problem linking to my WiFi but no internet when
lin
Regret to inform that an upgrade from 16.04 is also displaying the bug.
Reduced to using Google DNS on ipv4 (8.8.8.8) in order to work around it
David
On 14 Apr 2017 14:11, "David Oser" <1654...@bugs.launchpad.net> wrote:
I'm also experiencing this exact bug.
Upgrading from 16.10 to 17.04 did not
