On 05/19/12 04:13, Nilesh Govindrajan wrote: > On Sat, May 19, 2012 at 4:29 PM, Adam Carter <adamcart...@gmail.com> wrote: >>> Which is the best caching dns server? I'm presently using pdns-recursor, >>> which is quite good, but doesn't have option to set minimum ttl (doesn't >>> make sense, but some sites like twitter have ridiculously low ttl of 30s). >> The load balancing technology will be slow to respond if the TTLs are >> high, so given that responsive load balancing and timely fail over are >> good things, it does make sense. IIRC the F5 default is 20 seconds. Be >> careful if you are going to break DNS, there may be consequences >> you're not aware of. >> > I know that. Just experimenting things, because if I can cache it > locally, it would be quicker for me. > >>> Also, it isn't able to save cached entries to file so that it can be >>> restored on next boot. Any option? >>> >>> I am keeping my box 24x7 on because it serves as dns on my small home wifi, >>> not acceptable to me, because network is almost off at night (only phone) >>> and I have my router as secondary dns. >> Can you re-phrase that? - its hard to understand what the problem is. >> > Persistence across multiple boots/reboots. > > I found pdnsd which can do that, trying that out now. > You should really try changing you DNS server to some faster ones. I was having this same problem with my ISP or DSL modem with built in router taking a long time. I changed my DNS servers to Google DNS Servers (8.8.4.4 and 8.8.8.8) and haven't had a problem.
My setup is a little different but all in all I would really suggest you try a DNS server outside of your ISP. -- Willie Matthews matthews.wil...@gmail.com
