Hello Winfried,
> PowerDNS Recursor not listening at ::1 by default. But localhost resolves
> (/etc/hosts) to ::1 at the first try. So dig's first query fails.
> After 1 second (don't know why 1 second because default timeout is 3s), dig
> tries again at 127.0.0.1 and it works.
BINGO!
> You h
Hi Shamus,
PowerDNS Recursor not listening at ::1 by default. But localhost
resolves (/etc/hosts) to ::1 at the first try. So dig's first query
fails. After 1 second (don't know why 1 second because default timeout
is 3s), dig tries again at 127.0.0.1 and it works.
You have 3 possibilities:
On Tuesday, June 25, 2013, Shamus Smith wrote:
> Hello all,
>
> thanks for all your answers, but I'm still stuck. Below is the full output
> for dig for pdns and dnsmasq.
> The query time is 2 ms for the first uncached request and 0 ms for pdns
> and dnsmasq. However, the
> whole execution of the
Hello all,
thanks for all your answers, but I'm still stuck. Below is the full output for
dig for pdns and dnsmasq.
The query time is 2 ms for the first uncached request and 0 ms for pdns and
dnsmasq. However, the
whole execution of the dig command takes over 1 second for pdns and below 30 ms
f
Hello Shamus,
On Jun 22, 2013, at 1:39 , Shamus Smith wrote:
> However, a lookup always needs more than 1 second (query-time is 2 ms).:
> # time dig +short www.google.com @localhost
> 173.194.40.80
> 173.194.40.83
> 173.194.40.84
> 173.194.40.81
> 173.194.40.82
>
> real0m1.023s
> user0m0.
On Sun, Jun 23, 2013 at 5:40 PM, Michael Loftis wrote:
>
>
> I don't think anything other than /etc/hosts should get involved but your
> stall pretty clearly appears to be happening during the resolution of the
> @localhost and not the round trip to the world and through the pdns
> recursor.
On Sunday, June 23, 2013, Shamus Smith wrote:
> Thanks for your answer. The full dig output was in the first posting.
> I have not modified nsswitch.conf and /etc/hosts contains only this:
>
No, only the +short is in any of your responses, when I say full output I
mean without +short - there's a
Hi,
what does your recursor.conf look like? I'm only guessing here but as you
are obviously forwarding all queries to 8.8.8.8 there is one thing that
people tend to get the wrong idea about which is using forward-zones instead
of forward-zones-recurse which does not set the Recursion Desired (RD)
_
Von: Michael Loftis
An: Shamus Smith
CC: bert hubert ; "pdns-users@mailman.powerdns.com"
Gesendet: 18:44 Sonntag, 23.Juni 2013
Betreff: Re: [Pdns-users] 1 sec delay before DNS-answer at pdns-recursor
What about giving the full dig output too? My bet is you're actually
What about giving the full dig output too? My bet is you're actually
experiencing some sort of huge delay starting up dig or resolving
"localhost", use @127.0.0.1 instead and see if the time goes away.
Does your /etc/hosts contain 'localhost'? Have you modified your
nsswitch.conf? (Assuming stand
Hello Bert,
> > Any ideas why it takes so long?
>
> Rerun with --trace enabled and check what is happening. With some study, it
> should be clear what it is waiting for.
did that already before, but still did not found anything helpful there. Below
is a new trace.
btw, I am using 3.5.1 (packa
On Jun 22, 2013, at 1:39 AM, Shamus Smith wrote:
> Any ideas why it takes so long?
Rerun with --trace enabled and check what is happening. With some study, it
should be clear what it is waiting for.
Bert
___
Pdns-users mailing list
Pdns-users@ma
Hello all,
I installed pdns-recursor on my CentOS 6.4 machine with a simple config:
forward-zones=.=ISP-DNS-Server
setgid=pdns-recursor
setuid=pdns-recursor
However, a lookup always needs more than 1 second (query-time is 2 ms).:
# time dig +short www.google.com @localhost
173.194.40.80
173
13 matches
Mail list logo
