1 |
Willie Matthews wrote: |
2 |
> |
3 |
> |
4 |
> On 05/19/12 04:13, Nilesh Govindrajan wrote: |
5 |
>> On Sat, May 19, 2012 at 4:29 PM, Adam Carter <adamcarter3@×××××.com> wrote: |
6 |
>>>> Which is the best caching dns server? I'm presently using pdns-recursor, |
7 |
>>>> which is quite good, but doesn't have option to set minimum ttl (doesn't |
8 |
>>>> make sense, but some sites like twitter have ridiculously low ttl of 30s). |
9 |
>>> The load balancing technology will be slow to respond if the TTLs are |
10 |
>>> high, so given that responsive load balancing and timely fail over are |
11 |
>>> good things, it does make sense. IIRC the F5 default is 20 seconds. Be |
12 |
>>> careful if you are going to break DNS, there may be consequences |
13 |
>>> you're not aware of. |
14 |
>>> |
15 |
>> I know that. Just experimenting things, because if I can cache it |
16 |
>> locally, it would be quicker for me. |
17 |
>> |
18 |
>>>> Also, it isn't able to save cached entries to file so that it can be |
19 |
>>>> restored on next boot. Any option? |
20 |
>>>> |
21 |
>>>> I am keeping my box 24x7 on because it serves as dns on my small home wifi, |
22 |
>>>> not acceptable to me, because network is almost off at night (only phone) |
23 |
>>>> and I have my router as secondary dns. |
24 |
>>> Can you re-phrase that? - its hard to understand what the problem is. |
25 |
>>> |
26 |
>> Persistence across multiple boots/reboots. |
27 |
>> |
28 |
>> I found pdnsd which can do that, trying that out now. |
29 |
>> |
30 |
> You should really try changing you DNS server to some faster ones. I was |
31 |
> having this same problem with my ISP or DSL modem with built in router |
32 |
> taking a long time. I changed my DNS servers to Google DNS Servers |
33 |
> (8.8.4.4 and 8.8.8.8) and haven't had a problem. |
34 |
> |
35 |
> My setup is a little different but all in all I would really suggest you |
36 |
> try a DNS server outside of your ISP. |
37 |
> |
38 |
|
39 |
|
40 |
I agree. My ISP is AT&T and I changed my DNS to Google's too. It is |
41 |
very fast compared to AT&T's servers. I have had AT&T's servers not |
42 |
respond for several seconds but Google's just seem to work. |
43 |
|
44 |
Dale |
45 |
|
46 |
:-) :-) |
47 |
|
48 |
-- |
49 |
I am only responsible for what I said ... Not for what you understood or |
50 |
how you interpreted my words! |
51 |
|
52 |
Miss the compile output? Hint: |
53 |
EMERGE_DEFAULT_OPTS="--quiet-build=n" |