100% ping packet loss, and unable to ping or access internet, but can still resolve host names reddit / selfhosted ---------------------------------------------------------------------- RandomFun32 · 2023-12-18 22:24 Hello, My Debian 12 server has weirdly decided that it can't access the internet, can't ping domain names, but can ping IP address, able to update apt and even pull docker containers. When I ping a domain name, instead of saying it failed domain name resolution, it just says 100% packet loss, even when pinging gnu or google. I can also ping 1.1.1.1 and local IPs just fine. Traceroute and dig commands also work and are able to resolve the domains. I'm not able to find anything online outside of domain name resolution failures, any and all help is greatly appreciated. Thank you. ---------------------------------------------------------------------- adamshand · 2023-12-19 00:32 If you can ping 1.1.1.1 then it can access the internet. It's possible you have a bogus route that's trying to reach an internet IP on your local network? What do you get for `route -n`? Or perhaps you have some `iptables` rules that are blocking some things? What does `iptables -L -n` show? > When I ping a domain name, instead of saying it failed domain name resolution, it just says 100% packet loss What IP does it resolve to when you ping? What's in your `/etc/resolv.conf`? Can you manually use `host` to resolve domains using the name servers listed there? eg. `host www.google.com ` ---------------------------------------------------------------------- RandomFun32 · 2023-12-19 00:46 1. `Kernel IP routing tableDestination Gateway Genmask Flags Metric Ref Use Iface0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 enp2s00.0.0.0 192.168.68.1 0.0.0.0 UG 0 0 0 enp2s00.0.0.0 192.168.1.1 0.0.0.0 UG 100 0 0 enp2s0` 2. The output of that command doesn't mention anything that uses my network device, only docker containers 3. `nameserver 1.1.1.1` `nameserver 1.0.0.1` 4. Yes, `www.google.com has address 173.194.209.104` `www.google.com has address 173.194.209.103` `www.google.com has address 173.194.209.105` `www.google.com has address 173.194.209.147` `www.google.com has address 173.194.209.106` `www.google.com has address 173.194.209.99` `www.google.com has IPv6 address 2607:f8b0:4024:c02::93` `www.google.com has IPv6 address 2607:f8b0:4024:c02::68` `www.google.com has IPv6 address 2607:f8b0:4024:c02::69` `www.google.com has IPv6 address 2607:f8b0:4024:c02::67` ---------------------------------------------------------------------- adamshand · 2023-12-19 01:33 > Kernel IP routing tableDestination Gateway Genmask Flags Metric Ref Use Iface > 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 enp2s0 > 0.0.0.0 192.168.68.1 0.0.0.0 UG 0 0 0 enp2s0 > 0.0.0.0 192.168.1.1 0.0.0.0 UG 100 0 0 enp2s0 Not easy to read that, but it looks to me like you have three default routes? Unless you are doing something fancy, you typically only have on default route (0.0.0.0)? ---------------------------------------------------------------------- kmisterk · 2023-12-19 06:26 ## Post Removed Hey, RandomFun32! Thanks for your submission on selfhosted. Your post has been removed due to a violation of the purpose of the subreddit: **Self Hosting** ## Not Self-Hosted When it comes to posts regarding applications in this subreddit, they must feature a self-hosted tool, or a tool that *can be* self-hosted, or some kind of related information, help request, or otherwise related to a tool that is something that one can self-host. If you believe this post *is in fact* relevant to /r/selfhosted, feel free to [message the mods](https://www.reddit.com/message/compose/?to= /r/selfhosted&subject=Removed For Not Being Self- Hosted&message=[Removed Post](https://www.reddit.com/r/selfhosted/comments/18llg01/-/\)) with your concerns.