Originally posted by: sigs3gv
Try Posadis?
Originally posted by: spidey07
If his ISPs servers frequently take a long time to resolve or time out then it is very advantageous to run your own DNS server, plus it will cache any request it has made.
Originally posted by: BDawg
Originally posted by: spidey07
If his ISPs servers frequently take a long time to resolve or time out then it is very advantageous to run your own DNS server, plus it will cache any request it has made.
It'll cache it, but wouldn't your personal DNS server still forward lookup to the ISP servers? Wouldn't they still be the slow link?
Originally posted by: Rilex
The prefered method would be to configure forwarders, namely reliable forwards. Only after the forwarders fail should the roots be referenced.
I always use Verizon as forwarders:
4.2.2.3
4.2.2.4
They seem fairly reliable.
Originally posted by: Atheus
I was about to have a rant about how there's no point running a dns server for the caching alone, because the client should be caching anyway, but... it looks like windows makes an external request every time it gets URL rather than an IP address. In fact, a visit to anandtech.com generates up to 9(depending on the ads) seperate DNS requests and reloading the page generates them all over again. This sucks. Anyone know how to turn dns caching on in windows? in linux?
Originally posted by: Eltano1
Interesting, now I have a question. What are the address for the root?
Eltano