3

I know there is an easy fix to the problem by adding

nameserver 8.8.8.8

to /etc/resolve.conf but this is merely a hack and not a proper trouble shoot of the problem that caused the problem. If I am not wrong having the 'default'(or what do you call it ?) nameserver 127.0.0.53 should be enough on a fairly new Linux system (Ubuntu 16.04). I have gone through other related questions here and tried all those but to no avail. Some of the things I tried:

  1. Connecting through different NIC ( wlan0, Eth0 )
  2. configuring static IP (with google's DNS ) as well as dynamic IP ( with the default gateway [192.168.43.1] as the DNS.

But all without any success. I had some boot issues with the hard drive (my hard drive became unbootable for sometime because apparently there was some issue with bootloader which I fixed later with boot-repair).

In short, I can't ping google.com if there is nameserver 127.0.0.53 . But I can ping if I add nameserver 8.8.8.8

If anybody can help me to right direction that would be great. Thanks.

Update:

If it helps, I actually have dual boot system with Lubuntu 18.10 as well and it doesn't have the problem. the /etc/resolve.conf file has nameserver 127.0.0.53 .

0 Answers0