[Pdns-users] Problems with pdns-recursor

[bert hubert]

On Wed, Jan 31, 2007 at 02:09:24PM +0200, Andy Rabagliati wrote:

> > And show us the output while querying for the domain that has the problem.
> > Please include all logging from the start, and all 'dig' output.
> 
> I verified I have no old copies of pdns_recursor lying around.

Thanks.

> The machine musselcracker is our firewall. My desktop (quail) routes through it.
>  From my desktop (also ubuntu dapper), I see this :-

To recap:

dig on desktop: can talk to 72.212.18.41, can't talk to 76.212.18.42
dig on firewall: can't talk to 72.212.18.41, no data about 42

>From the trace:

> Jan 31 13:46:58 [1] visolve.com.: Resolved 'visolve.com.' NS ns1.visolve.com. to: 76.212.18.41
> Jan 31 13:46:58 [1] visolve.com.: Trying IP 76.212.18.41, asking 'visolve.com.|A'
> Jan 31 13:46:58 [1] visolve.com.: error resolving 

> Jan 31 13:46:58 [1] visolve.com.: Resolved 'visolve.com.' NS ns2.visolve.com. to: 76.212.18.42
> Jan 31 13:46:58 [1] visolve.com.: Trying IP 76.212.18.42, asking 'visolve.com.|A'
> Jan 31 13:46:58 [1] visolve.com.: error resolving 

>From the immediacy of the error, I'm betting you have a firewall somewhere
rejecting you - this is not a timeout.

Check if there are firewall rules on the pdns machine itself (iptables -L -n
-v), if that is not the case, run tcpdump on the pdns machine to see if
packets actually leave the computer.

To summarise, I don't think this is a PowerDNS problem.

Good luck!

-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://netherlabs.nl              Open and Closed source services