Occasionally, certain sites fail to load on Arch Linux.
Occasionally, certain sites fail to load on Arch Linux.
Hi there! Yesterday you set up Arch Linux with KDE on both a regular computer and a virtual machine using VirtualBox. Everything seems to be running smoothly, but you're facing problems with certain websites not loading. It's strange since sites like YouTube, Google, and others work perfectly. However, platforms such as Reddit, Twitter, and Github are completely inaccessible. You also can't install specific packages or apps. What should you try next? Thanks!
It means the system can't fetch the necessary information to load a resource. It could stem from a DNS problem, a certificate issue, or a general network failure. This often points to a connectivity concern rather than just a DNS error. The specific DNS server in use isn’t clear here. You might install dnsutils via sudo and then test with nslookup or another tool like curl.
The browser says it can't connect. Curl reports a failed connection to the website after a long wait, and the ping confirms the destination is unreachable. Changing the DNS server didn't help.
These alerts suggest a connection issue instead of a DNS problem. Verify both ip addr show and ip route commands display your network interface. Ensure the default gateway IP matches your card's network. If you run nslookup or dig, do you receive a reasonable result? The output shows a valid canonical name and address for github.com. A 3563 A record points to 140.82.121.4.
Your IP address appears to match the local network of the network card. The identical results from nslookup and dig suggest similar routing behavior, which could indicate a consistent network configuration or DNS caching issue.
This device is a Pi-hole. To set it up, refer to the official Arch Linux documentation: https://wiki.archlinux.org/title/Pi-hole
Your network appears to be functioning properly. All other devices—Windows, Android, etc.—work well within it. On your local machine, there’s no indication of any installation that might interfere with websites or similar services. You haven’t modified your local firewall settings.
The need for a Pi-hole isn't clear—it might be an installation error or incorrect files that can be resolved.