Hello Michael, On Tue, 8 Mar 2016 16:32:26 +0100 Bit World Computing - Michael Mertel <[email protected]> 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 8.8.8.8 as nameserver everything works as expected. > > This is somewhat strange, because 8.8.8.8 is the forwarding dns for my local > recursor. Do you use the `forward-zones-recurse`[1] or the `forward-zones`[2] option? When forwarding to google (8.8.8.8), the `forward-zone-recurse` option is needed (i.e. `forward-zones-recurse=.=8.8.8.8` 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`[3] 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. Best regards, Pieter 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 -- Pieter Lexis PowerDNS.COM BV -- https://www.powerdns.com _______________________________________________ Pdns-users mailing list [email protected] http://mailman.powerdns.com/mailman/listinfo/pdns-users
