The DNS server in question is the one you are currently querying or referencing.
The DNS server in question is the one you are currently querying or referencing.
This connects to a recent Linus video. The GRC DNS benchmark over ~35 minutes indicates your local IP 192.168.1.1 is significantly faster than any other DNS server. However, since that IP is your router, it’s unlikely the router itself acts as a DNS server. You probably have another DNS provider connected, but you’re unsure. Based on the results, does this confirm your current DNS server remains the fastest?
Your router will store certain addresses, making it quicker in specific scenarios. Google’s public DNS performs well, making it a solid choice. You might want to test 1.1.1.1 and 1.0.0.1, which are Cloudflare’s public DNS options.
As Oshino Shinobu from Monogatari mentioned, the router typically uses DNS first and caches data. But sometimes new requests are sent directly to the router instead of going through 8.8.4.4 before you receive anything. This marks your first real internet connection to a DNS server. I tested this with Cloudflare’s 1.1.1.1 and noticed a noticeable improvement in lag reduction. I recommend giving it a try and see how it affects your performance.
Ensure your router functions as a DNS server to resolve local network names. Without this, remote access like remote desktop won't work because it can't map the LAN IP for devices connected to it. Your router only knows IPs of machines directly linked to it. When searching a domain such as "google.com," it queries its DNS provider to determine the corresponding IP address. Additional insight: I struggled for a while until I understood that PiHole needed my router's IP as primary DNS and 1.1.1.1 as secondary to support name-based logging instead of IP addresses.