It's generally a DNS-related issue. Since Arch is now typically dominated by Systemed, you probally need to check the status of one of its deamones, systemd-resolved, which provides network name resolution to local applications.

In my case, the cause of this problem is that systemd-resolved wasn't running(inactive). So try to check its status first:

systemctl status systemd-resolved 

If you see that the value of Active field is inactive, you need to start it:

systemctl start systemd-resolved 

It's generally a DNS-related issue. Since Arch is now typically dominated by Systemed, it's likely that the problem lies with one of its daemons, systemd-resolved, which provides network name resolution to local applications.

So, the first step is to check its status:

systemctl status systemd-resolved 

If you see that the value of Active field is inactive, you need to start it:

systemctl start systemd-resolved 

In my case, the cause of this problem is that systemd-resolved wasn't running(inactive). So try to check its status first:

systemctl status systemd-resolved 

If you see that the value of Active field is inactive, you need to start it:

systemctl start systemd-resolved 

It's generally a DNS-related issue. Since Arch is now typically dominated by Systemed, you probally need to check the status of one of its deamones, systemd-resolved, which provides network name resolution to local applications.

In my case, the cause of this problem is that systemd-resolved wasn't running(inactive). So try to check its status first:

systemctl status systemd-resolved 

If you see that the value of Active field is inactive, you need to start it:

systemctl start systemd-resolved