Home/ Questions/Q 13599
Next
In Process

askthedev.com Latest Questions

Asked: 2024-09-26T23:08:56+05:30 In:

I am experiencing an issue with systemd-resolved not resolving any domain names on my Ubuntu system. Despite being correctly configured, it fails to provide DNS resolution. What steps can I take to troubleshoot and resolve this problem?

I’ve been having this frustrating issue with systemd-resolved on my Ubuntu setup. It’s supposed to handle DNS resolution, right? Well, it isn’t working at all for me. I’ve double-checked the configuration files, and everything looks fine. I’ve even rebooted my system, thinking maybe it just needed a fresh start, but nope—still no luck.

When I try to resolve domain names, it just doesn’t happen. I’ve run some basic tests; like using `ping` on common sites and checking `/etc/resolv.conf`, and it seems like systemd-resolved isn’t pulling any DNS servers or something. I thought maybe it’s a network issue, but my internet connection is working just fine since I can access websites directly through IP addresses.

I’ve seen some mention about the `systemd-resolve` command, but I’m not exactly sure what I should be looking for when I run it. There are also a bunch of logs in `journalctl`, but I don’t have a clue what to sift through or if they even contain anything helpful.

Has anyone dealt with this before? What’s the best way to troubleshoot this mess? Should I try stopping and restarting the `systemd-resolved` service? Or is there something more specific that I should be looking into?

I came across this potential fix online about editing some DNS settings, but honestly, I’m a bit hesitant to start messing with configurations I don’t fully understand. Not to mention, I worry about breaking something else.

If you’ve encountered a similar problem and managed to fix it, could you share what steps you took? I’m really in need of some solid guidance here. I’d love to get my DNS resolution back up and running so I can get back to being productive! Thanks in advance for any insights or suggestions; they would be much appreciated!

Share

    Leave an answer

    You must login to add an answer.

    Need An Account,

    2 Answers

    1. Systemd-resolved is indeed responsible for DNS resolution in Ubuntu, but issues can arise that prevent it from functioning properly. Since you’ve confirmed that your internet connection is active and that DNS isn’t resolving, it’s a good idea to start troubleshooting by checking the status of the systemd-resolved service. You can run the command sudo systemctl status systemd-resolved to see if it’s active and running without errors. If it is running but DNS queries still fail, try restarting the service with sudo systemctl restart systemd-resolved. Additionally, examine the contents of /etc/resolv.conf—it should point to the systemd resolver at 127.0.0.53. If it’s pointing elsewhere, that could indicate a configuration issue affecting DNS resolution.

      As for the systemd-resolve command, you can use it to check the current DNS settings and troubleshoot the resolution process. Running systemd-resolve --status will give you an overview of DNS servers currently being used. If the servers aren’t listed or are incorrect, you may need to manually set DNS servers in the resolved configuration. You can edit /etc/systemd/resolved.conf and specify your desired DNS servers there under the DNS= line. After making changes, remember to restart the service. If logs in journalctl show messages related to DNS resolution issues, you might find additional clues about the problem. Look for lines marked with systemd-resolved, which could direct you to solutions specific to your case.



    2. Help with systemd-resolved on Ubuntu

      Stuck with systemd-resolved? Here are some things to try!

      It sounds like you’ve been through a lot already! Systemd-resolved can be a bit tricky sometimes, especially if you’re not super familiar with it.

      Check the service status

      First off, let’s make sure that the systemd-resolved service is actually running. You can check its status with this command:

      systemctl status systemd-resolved

      If it’s not running, you can start it with:

      sudo systemctl start systemd-resolved

      Check the /etc/resolv.conf file

      Your /etc/resolv.conf file should be a symlink to /run/systemd/resolve/stub-resolv.conf. You can check this by running:

      ls -l /etc/resolv.conf

      If it’s not set up correctly, you might want to recreate that symlink like this:

      sudo ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

      Look for DNS servers

      Next, you could check the DNS servers that systemd-resolved is using. Run:

      systemd-resolve --status

      This will list all of the available DNS servers. If they’re missing or not what you expect, that might be part of the issue.

      Checking logs

      You can also look at the logs for any errors. Try:

      journalctl -u systemd-resolved

      Look for any warnings or errors that might indicate what’s going wrong.

      Restart the service

      If you see anything weird or just want to give it a refresh, you can stop and start the service again:

      sudo systemctl restart systemd-resolved

      Editing DNS settings

      As for editing DNS settings, it’s usually okay to try using a public DNS server like Google’s (8.8.8.8 and 8.8.4.4) or Cloudflare’s (1.1.1.1). You might find info on how to do this in:

      /etc/systemd/resolved.conf

      Just take a backup of the file before making changes, just in case!

      Keep It Simple

      Lastly, if you’re unsure about things, don’t hesitate to ask for help or reference the Ubuntu forums. There’s usually someone who’s been through the same issue!

      Good luck, and I hope your DNS resolution gets back on track soon!


    Related Questions