oh ok, so it would therefore ignore the router's setting
still I can set it up using that, and use Tomato blocklists for some other sites
He could block outgoing WAN UDP port 53 traffic coming from the LAN on the router though. That would prevent PC's on the LAN using anything but the router as their DNS.
He could block outgoing WAN UDP port 53 traffic coming from the LAN on the router though. That would prevent PC's on the LAN using anything but the router as their DNS.
I have used OpenDNS in the past but thought I'd give Be* DNS servers another go.
I wonder how many people in this thread are Be* users. It seems that whilst Be* is a popular ISP their DNS servers are not highly regarded?
When I used OpenDNS in the past, I never actually signed up. I will do this now and see what benefits I get and if it works better for me than just using their DNS servers.![]()
That sounds pretty poor.I'm with Nildram. Whilst Nildram used to have absolutely stellar DNS servers back in the old days ever since they were purchased by Pipex they turned to pot. Presumably because they just decommissioned their own DNS servers and pushed the requests onto Pipex's. Then when Pipex got bought out by Tiscali I suspect that Pipex just pushed all their DNS requests onto Tiscali. So that's 3 "invisible hops" that's DNS requests with Nildram are having to jump through.
That sounds good for you.Been using OpenDNS for a few days now and web pages load much more reliably now without timing out and me needing to sigh and press F5...