DNS resolves IPv6 instead of IPv4 on ping and pnpm. Recently Started.

ChrispyChris3 · 2023-10-12 03:20:07

The other day I was trying to get a project set up with pnpm and I was unable to connect and download any packages or anything. Finally I decided to see if I could even ping the server where I was trying to download the files from. That is when I found out ping wasn't working on any websites. However, ping would work if I typed in the IPv4 address, rather than using the name of the site. If I tried pinging via the name, it would do an IPv6 ping instead and just error out.

After I realized IPv6 was causing a problem, I found a command to turn it off temporarily, since I'm sure turning it off forever isn't ideal (neither is this network error). Turning off IPv6 instantly fixed all of the issues. I was able to download packages with pnpm and I didn't receive any more ping errors either, even if I didn't use the IPv4 address and instead just typed the URL out, things were working fine now.

This makes me wonder a couple things. 1. Why did this randomly begin causing me issues recently. A few months ago when I was last using pnpm and ping, I had no issues at all with IPv6 doing anything. Why is it suddenly giving me problems? 2. Is there any way to fix this odd issue while still allowing IPv6 to be used on the interface? I am willing to grab any logs or anything that might help someone understand what is going on.

Last edited by ChrispyChris3 (2023-10-23 02:17:33)

seth · 2023-10-12 07:10:35

ip a
ip r
resolvectl
stat /etc/resolv.conf
cat /etc/resolv.conf

https://wiki.archlinux.org/title/IPv6#P … _over_IPv6 and please adjust the subject of the thread to focus on the issue (DNS resolves IPv6 instead of IPv4) instead of some obscure symptom.

ChrispyChris3 · 2023-10-23 02:16:16

Thanks for your response and sorry for the obscure title and delay in getting back to this! Life had gotten a bit busy. I've recently updated the title in hopes that this entire thread can be more helpful.

I just updated that file and without restarting a service or doing anything else, it appears that everything works again. Well, at least the two things that I noticed were all of a sudden broken: ping via a website hostname and pnpm. I'm honestly unsure why either of those recently quick working, but I appreciate your help in getting things going again.

I'm curious if you know why this would suddenly become a problem out of nowhere.

Thanks!

seth · 2023-10-23 05:33:47

That's (still) DNS

resolvectl
stat /etc/resolv.conf
cat /etc/resolv.conf
nslookup google.com

Arch Linux

#1 2023-10-12 03:20:07

DNS resolves IPv6 instead of IPv4 on ping and pnpm. Recently Started.

#2 2023-10-12 07:10:35

Re: DNS resolves IPv6 instead of IPv4 on ping and pnpm. Recently Started.

#3 2023-10-23 02:16:16

Re: DNS resolves IPv6 instead of IPv4 on ping and pnpm. Recently Started.

#4 2023-10-23 05:33:47

Re: DNS resolves IPv6 instead of IPv4 on ping and pnpm. Recently Started.

Board footer