On Tue, Jun 15, 2010 at 05:10:11PM -0600, Darren Gamble wrote:
We just wanted to get some information on how the recursor behaves when
presented with a NS record set containing both IPv6 and IPv4 addresses,
and/or if a NS record name has both A and records.
If there a preference by the
Hi,
I've set up pdns_recursor and everything works as expected except one thing.
dig-ing reverse lookups returns nothing. With bind i have no such problems.
I've tested a bunch of IPs and I didn't get any answers.
Is this normal and pdns_recursor does not support this or there is a secret
Can you show your exact dig command line and the result from powerdns and bind?
This is all supposed to work :)
Sent from my phone.
- Reply message -
From: Uroš Gruber uros.gru...@gmail.com
Date: Wed, Jun 16, 2010 10:01
Subject: [Pdns-users] PDNS Recursor and reverse lookup
To:
Hi,
here is result from one of IP
[r...@host1 ~]#dig @91.185.194.202 118.167.130.182
; DiG 9.4.3-P2 @91.185.194.202 118.167.130.182
; (1 server found)
;; global options: printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NXDOMAIN, id: 7121
;; flags: qr rd ra; QUERY: 1, ANSWER: 0,
On Wed, Jun 16, 2010 at 10:34:30AM +0200, Uroš Gruber wrote:
Hi,
here is result from one of IP
Try adding -x to the command line. From the 'dig' manpage:
'The default query type is A, unless the -x option is supplied to indicate
a reverse lookup.'
[r...@host1 ~]#dig @91.185.194.202
On 06/16/2010 10:34 AM, Uroš Gruber wrote:
Hi,
Hello Uroš,
here is result from one of IP
[r...@host1 ~]#dig @91.185.194.202 http://91.185.194.202 118.167.130.182
I think you might have a mistake there.
The proper command with dig would be, -x is for reverse address lookup:
dig
bert hubert wrote:
On Tue, Jun 15, 2010 at 02:23:04PM +0100, Simon Bedford wrote:
It contains some other exciting stuff too, and it appears to be stable for
production use.
I have now built a static package and installed to 2 of the 8
servers after testing in isolation, they appear to be
On Wed, Jun 16, 2010 at 11:10:29AM +0100, Simon Bedford wrote:
I have been running the 'get tcp-clients' every 5 mins in cron on
both servers, one is very low 10 and fluctuates, the other is just
growing and growing and is currently at 55, hope this info is of
value for debug.
Is there any
Please see answers below :-
bert hubert wrote:
On Wed, Jun 16, 2010 at 11:10:29AM +0100, Simon Bedford wrote:
I have been running the 'get tcp-clients' every 5 mins in cron on
both servers, one is very low 10 and fluctuates, the other is just
growing and growing and is currently at 55, hope
Hi,
Do you have --trace output of what you describe? This is not expected
behaviour. Trace will show what is going on.
Bert.
Sent from my phone.
- Reply message -
From: Sebastian Laubscher sebastian.laubsc...@1und1.de
Date: Wed, Jun 16, 2010 11:04
Subject: [Pdns-users] pDNS Recursor
Hi again,
Do you have --trace output of what you describe? This is not
expected behaviour. Trace will show what is going on.
Sorry for the waste of time - I don't know how I produced this
behavior, but now everything works as expected.
Don't fuzzle with our test environment ;-)
Egg on my
dig ptr @91.185.194.202 118.167.130.182.in-addr.arpa
# dig ptr 60.42.39.24.in-addr.arpa
; DiG 9.4.3-P5 ptr 60.42.39.24.in-addr.arpa
;; global options: printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 52636
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0,
12 matches
Mail list logo
