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