Upgrade to 20.04.1 no internet

[Karl Auer]

On Sat, 2020-10-03 at 09:38 -0500, Chris wrote:
> Why Amazon is not found one minute and a successful ping the next I
> have no idea.

Because you still have a DNS problem (or one of your resolvers does).

amazon.com has a 60-second TTL, and a 60-second negative cache time.
After 60 seconds your system will perform another lookup. It will
remember the result, good or bad, for 60 seconds before it does another
lookup. So if every second or third lookup fails, you'll get
intermittent issues just like the ones you are seeing.

Google's TTL is five minutes, but the negative cache time is 60
seconds. If it works it'll work for five minutes, if it fails it'll
keep failing for 60 seconds.

I'm now about 90% certain that your problem, one way or another, is
with the DNS. If you use your DSL modem as your local resolver, and it
uses your ISPs nameservers, and one of them is playing silly-buggers,
that might explain it.

Try forcing your nameservers to 8.8.8.8 and see if the problem goes
away...

Also try doing a loooong ping sequence to 8.8.8.8 (100 - 1000 packets)
and see what the packet loss looks like. You may have lot of packet
loss, which would be another explanation for some but not all lookups
failing.

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer at biplane.com.au)
http://www.biplane.com.au/kauer

GPG fingerprint: 2561 E9EC D868 E73C 8AF1 49CF EE50 4B1D CCA1 5170
Old fingerprint: 8D08 9CAA 649A AFEF E862 062A 2E97 42D4 A2A0 616D