ludicolo @ ludicolo @lemmy.ml

Posts

25

Comments

114

Joined

9 mo. ago

Where was this motion when the continued resolution was on the floor? Fucking clowns.

KDE the customization is off the charts

Very helpful and enlightening comment, without this guidance I was lost.

This seems to have fixed it!! Thank you so much!

Yes the issue still arises

The issue fixes after the restart command but when I reboot it cimes back.

'ls -lh /etc/resolv*' spits out:

lrwxrwxrwx 1 root root 37 Mar 11 16:48 /etc/resolv.conf -> /run/systemd/resolve/stub-resolv.conf

-- Boot b3a9a949f8d1499fb0404672a02d2e34 -- Mar 11 21:04:21 arch systemd[1]: Starting Network Name Resolution... Mar 11 21:04:21 arch systemd-resolved[1296]: Positive Trust Anchors: Mar 11 21:04:21 arch systemd-resolved[1296]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Mar 11 21:04:21 arch systemd-resolved[1296]: . IN DS 38696 8 2 683d2d0acb8c9b712a1948b27f741219298d0a450d612c483af444a4c0fb2b16 Mar 11 21:04:21 arch systemd-resolved[1296]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.a rpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 170.0.0.192.in-addr.arpa 171.0.0.192.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa ipv4only.arpa resolver.arpa corp home internal intranet lan local private test Mar 11 21:04:21 arch systemd-resolved[1296]: Using system hostname 'arch'. Mar 11 21:04:21 arch systemd-resolved[1296]: mDNS-IPv4: There appears to be another mDNS responder running, or previously systemd-resolved crashed with some outstanding transfers. Mar 11 21:04:21 masonarch systemd-resolved[1296]: mDNS-IPv6: There appears to be another mDNS responder running, or previously systemd-resolved crashed with some outstanding transfers.

Yeah I am positive I am running systemd

I can ping 1.1.1.1 and localhost but pinging google.com comes up with "temporary failure in name resolution"

I was able to get internet working by running the cimmand suggested by badlotus (I had already deleted the file they told me to the first time and then run the cimmand. So i didn't delete it again because it was gone.) When I run that command my internet cimes back. However if I restart the issue comes back.

None of those config files exist in that folder location.

So I was able to get it working again by doing this solution that badlotus suggested. I did not delete the file because it was already gone after the first timw I attempted this. If I reboot my device however the issue comes back. If I run the command again my internet is back.

Badlotus' solution:

"Have you tried deleting /etc/systemd/resolved.conf and restarting the service with systemctl restart systemd-resolved?"

Ok wtf. I retried this solution and it worked for some reason. I have no idea what happened differently. I didn't delete the file because it was already gone.

However if I restart it breaks again.

I no longer have tailscale installed. i uninstalled it thinking that would fix it. I cannot reinstall it now because I can't cinnect to the internet.

I still am getting somw data transfer it looms like. I can see my upload and down load speed fluctuating. It just shows a yellow triangle by my ethernet icon and says "limited connection".

I did and thay did not change anything.

As of right now I have tailscale uninstalled so I will reinstall it and try the values again.

EDIT: lol I forgot I do not have internet I cannot reinstall tailscale

EDIT 2: Pinging 1.1.1.1 works

That did not work, I deleted the file and then I restarted the service. I then restarted the pc just to make sure. Still no internet access and still same limited connectivity error.

No I did not edit this at all. Bkth were set to the value '2'

I changed them both to 0 and 1 and it did not fix my issue 🫤

○ systemd-resolved.service - Network Name Resolution Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; preset: enabled) Active: inactive (dead) Docs: man:systemd-resolved.service(8) man:org.freedesktop.resolve1(5) https://systemd.io/WRITING_NETWORK_CONFIGURATION_MANAGERS https://systemd.io/WRITING_RESOLVER_CLIENTS

Yes it does

I try to nano into my resolv.conf but it appears to only be a symbolic link file. I apologize for my ignorance but is there any other way to revert my dns back?

EDIT: the symbolic link leads to a directory that does not exist:

/run/systemd/resolve/stub-resolv.conf

This is the guide I followed:

https://tailscale.com/kb/1036/install-arch

I then restarted because I was getting several errors when trying to use the tailscale up command.

After thay restart I was able to get tailscale up to work but that is when the issue with limited connectivity arose.