Realy strange. Ok let's try step by step.
Does your authoritative DNS Server work? Log-in into your DNS Server and
dig -p 5300 @127.0.0.1 -x 10.20.0.4
dig -p 5300 @127.0.0.1 -x 10.20.1.4
dig -p 5300 @127.0.0.1 -x 10.20.2.4
And please provide the whole output.
If this works, test your Recursor.
> Maybe you didn't stopped it before you restarted? In this case config changes
> didn't apply to the (running) Recursor.
Well I just did a service pdns-recursor restart
So I did some more testing and I found something else: it doesn't change my
problem, but it does make the problem worse ;
Am 26.09.2014 09:38, schrieb Bart-Jan van Hummel:
> I don't know why he gives that resonse, since only pdns-recursor is
> using port 53 on UDP/TCP:
>
> ~ root# netstat -tulpn | grep 10.20.0.4:53
> tcp0 0 10.20.0.4:530.0.0.0:*
> LISTEN 3134/pdns_recursor
>
Hello All,
Please upgrade BASH.
yum clean all
yun install bash
https://access.redhat.com/announcements/1210053
Thanks,
Ravi.
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
From: "abang"
To: pdns-users@mailman.powerdns.com
Sent: Friday, 26 September, 2014 7:36:13 AM
Subject: Re: [Pdns-users] PDNS does not send info for reverse DNS
Hi Winfried
> Hi,
>>Exception: Resolver binding to server socket on port 53 for 10.20.0.4:
>>Address already in use
> Please
Hi Peter,
Sent: Thursday, 25 September, 2014 4:33:43 PM
> A quick response to just this part: you can set dont-query to empty to avoid
> this. Let us know if it helps!
Unfortunately it didn't change anything.
I am also tailing the syslog but it seems the reverse query for 10.20.0.2 does
