[Pdns-users] pdns-recursor 0.0.759g02abb90-1 (4.0 master) vs. getent?
pieter.lexis at powerdns.com
Tue Mar 8 17:57:31 UTC 2016
On Tue, 8 Mar 2016 16:32:26 +0100
Bit World Computing - Michael Mertel <michael.mertel at bwc.de> wrote:
> I was wondering why an apt-get update cannot resolve repo.powerdns.com, but a ping is able to do so. This only happens if /etc/resolv.conf points to my recursor. If I use 184.108.40.206 as nameserver everything works as expected.
> This is somewhat strange, because 220.127.116.11 is the forwarding dns for my local recursor.
Do you use the `forward-zones-recurse` or the `forward-zones` option? When forwarding to google (18.104.22.168), the `forward-zone-recurse` option is needed (i.e. `forward-zones-recurse=.=22.214.171.124` in your recursor.conf). This will set the Recursion Desired-bit on the query sent out. Google sends SERVFAIL to clients without the RD-bit set.
If this is the case and you still have these issues, could you enable the `trace` option and query your local resolver for repo.powerdns.com and email the traces?
> Maybe it’s how the apt-get tries to resolve the name? The only thing I found was, that getent is not returning the correct results.
apt, ping and getent all seem to use the getaddrinfo(3) call.
> Is this a known bug? Never had any trouble with the 3.7.3 release.
This is not a known bug. We'll await your test results.
1 - https://doc.powerdns.com/md/recursor/settings/#forward-zones-recurse
2 - https://doc.powerdns.com/md/recursor/settings/#forward-zones
3 - https://doc.powerdns.com/md/recursor/settings/#trace
PowerDNS.COM BV -- https://www.powerdns.com
More information about the Pdns-users