#[SOLVED] DNS not resolving

58 messages · Page 1 of 1 (latest)

silk obsidian
#

I booted up my computer this morning and I found out that my DNS resolver was not resolving any dns, I get connect to Google and cloudfairs normal ones, but I couldn't connect to any domain names. I tried to do some troubleshooting, but nothing prevailed, please help.

spring silo
#

.aw network configuration

exotic galeBOT
acoustic pagoda
silk obsidian
#

Oh wait, no, that's /etc/systemd/resolved.conf

#

resolv.conf says nameserver 192.168.0.1

acoustic pagoda
silk obsidian
silk obsidian
silk obsidian
#

@acoustic pagoda empty reply from server

#

No wait, I did it again and it was fine

#

What do I do next?

acoustic pagoda
silk obsidian
#

Nothing comes out

acoustic pagoda
silk obsidian
#

Sorry bad quality, I can't copy paste because.. well, no internet

acoustic pagoda
#
ip route show default
silk obsidian
#

Default via 10.0.0.1 Dev wlan0 Proto DHCP SRC 10.0.0.63 metric 600

silk obsidian
acoustic pagoda
#
  • side note: You may consider masking the IPv6 address in the output in the future, as these are public addresses.
silk obsidian
#

Oh shizer

#

You're right

#

Anyway, how screwed am i?

acoustic pagoda
silk obsidian
#

No output

acoustic pagoda
silk obsidian
#

Oh

acoustic pagoda
#
ping -c4 192.168.0.1
silk obsidian
#

100% packet loss

#

What should I put as the name server?

acoustic pagoda
# silk obsidian 100% packet loss

You may want to consider using systemd-resolved, as it will automatically deduce the appropriate DNS server to use. Addtionaly, it will cache the lookup results to speed up the process.

silk obsidian
#

I am using systemd-resolved

acoustic pagoda
silk obsidian
#

Oh

#

Well how do I fix it?

#

And the resolved service is active and enabled

acoustic pagoda
silk obsidian
#

Ok, done

acoustic pagoda
silk obsidian
#
one.one.one.one: resolve call failed: lookup failed due to system error: connection refused
silk obsidian
#

What now?

acoustic pagoda
silk obsidian
#

NetworkManager.service

acoustic pagoda
#

Please also post the contents of your /etc/systemd/resolved.conf file.

silk obsidian
silk obsidian
acoustic pagoda
#

Please run the following command to find out if you have manually set the DNS server in the Network Manager connection file by running

nmcli connection show <name of the connection from the previous output>.

If so, please clear the ipv4.dns field and set ipv4.method to manual.

If there is no suspicious configuration, please try the following command

resolvectl dns wlan0 1.1.1.1

And test your DNS again

AFK, Out.

silk obsidian
#

@acoustic pagoda sorry, I know you just said you were afk, but that still didn't work. I replaced the DNS in my main connection and it's not working

spring silo
#

systemctl status systemd-resolved
See if it's active

silk obsidian
#

@acoustic pagoda so I just got flustered and decided to reinstall, but now audio is only working on my headset and not on my speakers. I'm using pulse audio, what should I do?

silk obsidian
#

@acoustic pagoda help I got it working a bit, but I can't change the volume, but now it's not working at all again

silk obsidian
#

Never mind I just installed pipe wire