DNS cache handles domain name lookups, while DHCP manages IP address assignments.
DNS cache handles domain name lookups, while DHCP manages IP address assignments.
I've seen online discussions suggesting that you shouldn't directly instruct the DHCP server to supply alternative DNS servers. Doing so would cause the router to rely on its own cached entries, which can slightly improve performance. However, DNS benchmarks often highlight that most routers offer limited and weak DNS resolution capabilities. If the DNS servers your router uses aren<|pad|>, they might not function optimally. Users employing GRC's DNS Spoofability tools have found that consumer routers can be disrupted by certain DNS responses, potentially exposing network access to external threats. Many such devices lack comprehensive DNS lookup functions. This issue was likely identified in performance tests and shared here. Suggested steps: Unless you have a compelling reason, consider turning off your router's DNS services (it currently does for all devices). Rebooting your devices afterward may expose the multiple DNS servers your ISP provides. This setup is better than relying on a single, underpowered router as an intermediary. What are your thoughts? How do you handle this situation?
These terms refer to how DNS works and its performance issues. It can seem inefficient if the software or tools used don’t cover all necessary records. A delay of about 3ms might happen depending on the setup. Sometimes manufacturers create their own DNS solutions, which may not support certain records. If your router handles DHCP, it assigns DNS addresses automatically. Setting it to a known service like 8.8.8.8 or 1.1.1.1 can direct queries to those providers. If your router acts as a DNS server, its behavior depends on whether it caches data or forwards queries to another server. Running as a proxy means it only forwards requests without processing them deeply. For most users, these concerns aren’t major unless you’re in regions with unreliable ISPs or public networks. Security updates for routers are rare, so risks are lower unless someone interferes with DNS traffic. Crashing devices or privilege attacks are separate issues.
They don't trust the built-in DNS service because it can be set up incorrectly and is prone to DOS attacks, changing a lot between vendors. You should be able to direct it straight to your chosen resolver instead of depending on the router. If you have an extra VM or Raspberry Pi, set up a proxy like Pihole to manage the requests.
I saw that even when you set the DNS server in DHCP, calls still go through the router. The issue is: 1) leaving DNS blank in DHCP, or 2) entering a router IP like 192.168.x.x. 2) setting a specific DNS server in DHCP to replace the router's DNS. Which is preferable? Right now I’m using option 1 with Quad9.