Skip to main content

Ubuntu DNS issue fix DNS_PROBE_FINISHED_BAD_CONFIG

Issue 

I've been playing with a VPN and somehow it messed up my DNS resolution configurations. Chrome gives DNS_PROBE_FINISHED_BAD_CONFIG error and can't ping google. So it seemed to be an issue with the DNS. Of course, restarting didn't fix it.

I tried DNS lookup which gave me below.

error nslookup google.com

To make sure this is somehting to do with my DNS confgis, I ran the same by providing the google DNS servers. 

nslookup with google dns


It works, which means my default DNS is not working for some reason.

To make sure this, ran the below command.

systemd-resolve --status

Output has an entry for DNS Servers, which was ::1

Fix


1. Edit the file /etc/systemd/resolved.conf.

sudo vi /etc/systemd/resolved.conf

2. Add new DNS entries. I added 2 google DNS and the cloudflare DNS sever.
[Resolve]
DNS=8.8.8.8 8.8.4.4 1.1.1.1

3. Restart the systemd-resolved and check the configuration is persisted in /run/systemd/resolve/resolv.conf file.

sudo service systemd-resolved restart
cat /run/systemd/resolve/resolv.conf

Same contents you added should be there.

4. Delete the symlink to /etc/resolv.conf

sudo rm /etc/resolv.conf

5. Create a new symlink

sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

6. Restart the service agian

sudo service systemd-resolved restart

7. To check if this is working, run the nslookup with default name server.

Nslookup google.com


So, I'm back online!
Hope this helps.



Labels:

Comments

  1. AnonymousDecember 18, 2022 at 8:14 PM

    I was really helpful. Could you imagine i relied on a vpn for like a week.

    ReplyDelete
  2. AnonymousOctober 13, 2023 at 2:46 AM

    Thanks a lot for this working hint

    ReplyDelete

Post a Comment

Popular posts from this blog

Install Docker on Windows 11 with WSL Ubuntu 22.04

This is to install Docker within Ubuntu WSL without using the Windows Docker application. Follow the below steps. Install Ubuntu 22.04 WSL 1. Enable Windows Subsystem for Linux and Virtual Machine platform Go to Control Panel -> Programs -> Programs and Features -> Turn Windows features on or off 2. Switch to WSL 2 Open Powershell and type in the below command. wsl --set-default-version 2 If you don't have WSL 2, download the latest WSL 2 package and install it.  3. Install Ubuntu Open Microsoft Store and search for Ubuntu. Select the version you intend to install. I'd use the latest LTS version Ubuntu 22.04. Click on the Get button. It will take a couple of minutes to download and install. 4. Open up the installed Ubuntu version that was installed. If you get an error like the below image, make sure to install the WSL2 Kernel update .  If it's an older Ubuntu version the error message would be something like the image below. Error: WSL 2 requires an update to its
1 comment
Read more

How to fix SSLHandshakeException PKIX path building failed in Java

TL ; DR 1. Extract the public certificate of the website/API that you are trying to connect from your Java application. Steps are mentioned in this post 2. Use the Java keytool to install the extracted certificate into the "cacerts" file (Trust store) keytool -import -trustcacerts -alias <domain name> -file <public certificate>.cert -keystore /path_to_java_home/jre/lib/security/cacerts -storepass changeit 3. Restart your Java application Exception A typical exception stack trace would look like below. javax.net.ssl. SSLHandshakeException : sun.security.validator.ValidatorException: PKIX path building failed : sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1959) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302) at sun.security.ssl.Handshake
Post a Comment
Read more

Automatically open Chrome developer tools in a new tab

Sometimes we need to check the console or the network transactions of a link that opens up in a new tab. By default, the Chrome developer tools are not opening in a new tab. So, by the time when we hit F12 and open the dev tools, part of the information we needed could be already gone.  There's a setting in dev tools where you can keep the dev tools open automatically in a new tab. To enable that, hit F12 and open up the dev tools. Click on the settings icon in the top right corner. In the Preferences section, scroll down to the bottom. You'll be able to find the option to Auto-open DevTools for popups. Select the checkbox and we're good to go!
Post a Comment
Read more