After some more testing: local-address=0.0.0.0/32
throws an error. local-address=0.0.0.0 works, reports that the pdns_recursor is listening on "0.0.0.0", and appears to make it listen on all interfaces. However, this is undocumented in https://doc.powerdns.com/md/manpages/pdns_recursor.1/ as well as in the pdns_recursor's manual page. Opened https://github.com/PowerDNS/pdns/issues/2873 to keep track of this. ________________________________________ From: Rob Locke [roblo...@gmail.com] Sent: Saturday, November 7, 2015 16:26 To: a b Cc: pdns-users@mailman.powerdns.com Subject: Re: [Pdns-users] How to get pdns_recursor to listen on all interfaces? I don't know if this has changed in the latest release, but the only way I could do it was to explicitly list the interface IP addresses in the local-address directive. =( Rob On Saturday, November 7, 2015, a b <tripivc...@hotmail.com<mailto:tripivc...@hotmail.com>> wrote: What is the syntax to specify that pdns_recursor listen on all interfaces (something like "0.0.0.0/32<http://0.0.0.0/32>")? The issue I am facing is that, not knowing whether this is even possible, I am unable to automate this. As far as I am aware, there is no way of reliably detecting the primary network interface on a multi-homed host, as per definition, a multi-homed host is a gateway for multiple networks and none of the networks has precedence over the other. What I am trying to avoid is hard coding interface names or internet protocol addresses into the "local-address=..." configuration line in recursor.conf(4). _______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users _______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
