Think you can only get aa if the the server is an authority
I've been playing around with a local forward first caching server so I
tried it.
First run:
% dig mail.com
; <<>> DiG 9.9.2-rpz.066.22-P1 <<>> mail.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, sta
Matus UHLAR - fantomas wrote:
>
> this is clearly a cached answer (aa flag is missing). How did you come to
> the conclusion that caching does not work?
It's probably a cached answer from one of the forwarders. The response
time from the server was too long for it to be locally cached.
Tony.
--
On 15.03.13 15:25, Abdellatif ... wrote:
I want to optimize the call to remote dns server to resolve domain names
each time needed. What i want to do is that if the hostname is
requested for the first time than call the remote dns (for example
8.8.8.8) to resolve it, once called then recorded for
forwarders {
208.67.220.220;
208.67.222.222;
8.8.8.8;
};
on a semi-related note, i'd encourage you to not use forwarders. bind is
perfectly happy to lookup and cache any data necessary on its own.
-ben
__
Abdellatif ... wrote:
>
> It doesn't seem to use the cache, here is the call of dig mail.com :
If you dig it twice do you get a faster response?
Tony.
--
f.anthony.n.finchhttp://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or
Hello;
I want to optimize the call to remote dns server to resolve domain names
each time needed. What i want to do is that if the hostname is
requested for the first time than call the remote dns (for example
8.8.8.8) to resolve it, once called then recorded for later use in such
way when ne
6 matches
Mail list logo
