Upgrade to 20.04.1 no internet

[Colin Law]

On Sat, 3 Oct 2020 at 15:39, Chris <chris.pollock1948 at gmail.com> wrote:
>
> Google:
> ping -c5 209.85.128.0
> PING 209.85.128.0 (209.85.128.0) 56(84) bytes of data.
>
> --- 209.85.128.0 ping statistics ---
> 5 packets transmitted, 0 received, 100% packet loss, time 4076ms

That doesn't work for me either

>
> Another Google V4 IP
> chris at localhost:~$ ping -c5 216.239.32.0
> PING 216.239.32.0 (216.239.32.0) 56(84) bytes of data.
>

Nor does that one work.

> --- 216.239.32.0 ping statistics ---
> 5 packets transmitted, 0 received, 100% packet loss, time 4101ms
>
> chris at localhost:~$ ping -c5 amazon.com
> ping: amazon.com: Name or service not known
>
> chris at localhost:~$ ping -c5 amazon.com
> PING amazon.com (176.32.103.205) 56(84) bytes of data.
> 64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=1 ttl=239
> time=58.3 ms
> 64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=2 ttl=239
> time=58.3 ms
> 64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=3 ttl=239
> time=58.5 ms
> 64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=4 ttl=239
> time=58.2 ms
> 64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=5 ttl=239
> time=58.0 ms
>
> --- amazon.com ping statistics ---
> 5 packets transmitted, 5 received, 0% packet loss, time 4004ms
> rtt min/avg/max/mdev = 58.004/58.269/58.477/0.154 ms
>
> Why Amazon is not found one minute and a successful ping the next I
> have no idea.

That suggests an intermittent DNS problem.  You could try setting the
server manually to 8.8.8.8 to see what happens.

Colin