Hi all, I have a PDNS server set up with a zone and reverse zone for our domain (here 1.2.3.4), and have the recursor configured to forward requests not in our recognized zones to another DNS server on the network (here 1.2.0.4). While this works fine for hostname lookups, it doesn't seem to work for reverse DNS. If I dig an IP that is in PDNS' reverse zone, that works fine, but any other IP's fail outright.
; <<>> DiG 9.7.0-P1 <<>> -x 8.8.8.8 @ns1.example.local ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12863 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;8.8.8.8.in-addr.arpa. IN PTR ;; AUTHORITY SECTION: in-addr.arpa. 86400 IN SOA ns1.example.local. hostmaster.example.local. 2012103103 28800 7200 604800 86400 ;; Query time: 1 msec ;; SERVER: 1.2.3.4#53(1.2.3.4) ;; WHEN: Tue Nov 6 10:22:15 2012 ;; MSG SIZE rcvd: 106 and syslog shows Nov 6 06:49:25 example-dns pdns_recursor[28151]: Failed to update . records, RCODE=2 It seems PDNS is onl looking at the authoritative zone, how can I get these to resolve with the recursor that is configured? My versions are server 3.1 and recursor 3.3. Config files are: pdns.conf: allow-recursion=10.0.0.0/8,192.168.0.0/16 allow-recursion-override=off daemon=yes disable-axfr=yes guardian=yes launch=gmysql lazy-recursion=yes local-address=1.2.3.4 local-port=53 recursor=1.2.0.4 recursor.conf: forward-zones= example.local=1.2.3.4, other.net=1.2.0.4, 3.2.1.in-addr.arpa=1.2.3.4 local-address=127.0.0.1 local-port=53 Many thanks, Gordon -- View this message in context: http://old.nabble.com/PDNS-Reverse-DNS-lookup-recursion-tp34646567p34646567.html Sent from the PowerDNS mailing list archive at Nabble.com. _______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users