127.anything is going to be localhost. That is, some service on the same computer is doing DNS resolution for you.
You problem is either routing or DNS resolution. Try pinging 4.2.2.2 and google.com. If you can ping the numeric address but not the domainname, then your problem is DNS. If you can't ping either one, then your problem is routing. On Sat, Feb 22, 2020 at 10:32 PM John Jason Jordan <[email protected]> wrote: > On Sun, 23 Feb 2020 00:21:07 -0500 > [email protected] dijo: > > >I assume that you are using network manager (NM) - you do not say. > >If yes: > > * what is in your /etc/resolv.conf? > > * If you see something else than your router just delete the file as > > root and reconnect to the network using NM - it will recreate > >new /etc/resolv.conf > > The only things in /etc/rsolv.conf are: > > nameserver 127.0.0.53 > search lan > > Above in the # lines it says #127.0.0.53 is the systemd-resolvd stub > resolver. > > It doesn't seem to be very effective at resolving things. > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
