DNS failing doesn't mean that the internet is down or your access is broke. It just means that DNS isn't working.
See if you can ping a well-known IP -
Does that work? If it does, it is just a DNS issue, nothing more.
If that ping fails, try to ping your router. I don't know the IP address, but 192.168.0.1 is common. You'll need to figure that out.
To get your configured gateway - usually your router, use:
Code:
read -r x x i x< <(ip r g 1);echo "$i"
Then try to ping the IP returned by that command. Or do it all in 1 command:
Code:
ping -c 2 $(read -r x x i x< <(ip r g 1);echo "$i")
If that works, then try rebooting the router and checking other systems on the LAN for issues.
If that doesn't work, we need some information about the network devices in your computer. This is where it gets harder, since the easy ways to get that information are using tools that aren't installed by default - so if you haven't installed them, it will get ugly. Anyway, the easy commands are:
Code:
inxi -Nx
# or
lshw -C network
Either is fine.
If those say Command not found, or something like that, then we have to do it the harder way:
Code:
lspci -vk |egrep --after-context=8 'Ethernet|Network'
# or
lspci -vk |perl -lne 'print if /Ethernet|Network/ .. /^[\w]*$/'
The last command is the most flexible, but getting the spacing correct is less easy.
From there, we can decide what to do. Hopefully, the first ping 8.8.8.8 command works. If so, stop and let us know that.
Bookmarks