Using Lan Cache as the DNS server in your router blocks internet access
Using Lan Cache as the DNS server in your router blocks internet access
Hello, I set up a LanCache similar to the video from four months ago. https://www.youtube.com/watch?v=wWltASCJO-U&t=786s The process went smoothly until now. I tested it on a machine where I manually configured the DNS to point to the LANCache server. It performed exceptionally well, doubling the speed. Ideal. Then I connected it to my home network. The Upstream_DNS was set to my PiHole's IP address. I used an AVM FritzBox as a router. In the DNS Server section, I changed the IP from PiHole to LANCache and made this adjustment in the home network tab under Network settings. Now, my PC is not getting internet access. Am I making a mistake? Why isn't the internet working? When I revert the DNS back to PiHole, it functions without issues. It also worked when LANCache's DNS was configured only in Windows. If you need further details, I'll gather more information.
A PiHole already acts as a DNS cache, no real reason to add another one to the mix: https://docs.pi-hole.net/ftldns/dns-cache/ Changing the router's DNS isn't really needed, you primarily need to change the DNS in the DHCP server settings so the machines connected to the router get the DNS auto-configured. If you no longer get internet access (I assume you still have access, it's more like the machines can no longer resolve IPs), then you'd need to test if the machines can reach the cache and whether name resolution works properly (e.g. "nslookup <some name> <ip of cache>")
I'm sorry, I still can't grasp the reason. The screenshots show the IP changes made to DNS. In Lancache, "UPSTREAM_DNS" is set to 192.168.178.46, which might matter because Proxmox should handle everything from there—router and DHCP, not Proxmox itself. Every x.x.x.46 was updated to 47, which Proxmox didn't consider.
Just to be sure: You did not change the upstream DNS server of the Pi-hole to 192.168.178.47? I hope not, otherwise you're creating a loop. Meaning: Lancache should use Pi-hole as its upstream DNS server Pi-hole should use e.g. 1.1.1.1 as its upstream Everything else should then use the Lancache (configured through the DHCP) So your PCs will run to the Lancache, if it doesn't know the answer (yet) it'll go to the Pi-hole and if that one doesn't know the answer it'll go to some external DNS provider. But as I said above, there's no real point to a Lancache in a network that already has a Pi-hole, because the Pi-hole acts as a DNS cache already. I would run some benchmarks to see if it makes any difference. For example if you have Linux somewhere you should be able to use "dig" for that purpose: dig @1.1.1.1 | grep "Query time";; Query time: 19 msec dig @<local-dns-ip> | grep "Query time";; Query time: 3 msec
I confirmed that the cache wasn<|pad|>, not the upstream. I understood 2 DNS entries aren't ideal, but I needed a Steam/games cache to avoid re-downloading in Germany. My initial plan was PC → Lancache → Pihole → Internet, but it didn't work. Now I've reset everything so the router relies solely on Pihole.
It should be simple enough. Uncertain about the issue. If it remains linked to the network, run the command in the (Windows/Linux) terminal to target DNS queries: nslookup 192.168.178.47. If successful, it likely works with DHCP-configured DNS. Check if firewall rules on Lancache block DNS requests.
Eigenvektor nslookup 192.168.178.47 DNS request failed. Timeout occurred after 2 seconds. Server reported unknown address with timeout. DNS request timed out again, timeout was 2 seconds. DNS request timed out multiple times with a 2-second delay. DNS request timed out repeatedly. Time exceeded for UnKnown request. It appears the server is listening on port 53, but opening it wasn't specified in documentation.
I believe I located the issue—it was likely Layer 8, which is me. I restarted the server, but it appears Docker Compose didn’t start properly. The router’s DNS settings haven’t been changed yet; I’ll update them tomorrow when no one is home.