| 1 |
On Sat, May 19, 2012 at 10:06 PM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 2 |
> On Sat, 19 May 2012 07:45:56 +0530 |
| 3 |
> Nilesh Govindrajan <contact@××××××××.com> wrote: |
| 4 |
> |
| 5 |
>> Hi, |
| 6 |
>> |
| 7 |
>> Which is the best caching dns server? I'm presently using |
| 8 |
>> pdns-recursor, which is quite good, but doesn't have option to set |
| 9 |
>> minimum ttl (doesn't make sense, but some sites like twitter have |
| 10 |
>> ridiculously low ttl of 30s). Also, it isn't able to save cached |
| 11 |
>> entries to file so that it can be restored on next boot. Any option? |
| 12 |
> |
| 13 |
> You can use almost any cache you want... |
| 14 |
> |
| 15 |
> ... except bind |
| 16 |
> |
| 17 |
> We use unbound. Does the job, does it well, developer very responsive. |
| 18 |
> |
| 19 |
> But do not fiddle with TTLs, that breaks stuff in spectacular ways. |
| 20 |
> Essentially, with the TTL the auth server is saying "We guarantee that |
| 21 |
> you can treat this RR as valid for X amount of time and suffer no ill |
| 22 |
> effects if you do" |
| 23 |
> |
| 24 |
> What you want to do is break that agreement, which is really not s good |
| 25 |
> idea. |
| 26 |
> |
| 27 |
>> |
| 28 |
>> I am keeping my box 24x7 on because it serves as dns on my small home |
| 29 |
>> wifi, not acceptable to me, because network is almost off at night |
| 30 |
>> (only phone) and I have my router as secondary dns. |
| 31 |
> |
| 32 |
> Just use Google's caches or OpenDNS. They do the job so much better |
| 33 |
> than you ever could. Why reinvent the wheel? |
| 34 |
> |
| 35 |
> |
| 36 |
|
| 37 |
Slow connection. See my previous reply to the list. I'm using pdnsd, |
| 38 |
which can persist records and has every damn feature I wanted. |
| 39 |
|
| 40 |
-- |
| 41 |
Nilesh Govindarajan |
| 42 |
http://nileshgr.com |
Archives