Hello,
For the archives: 0.0.0.0 has always worked -somewhat- but could cause
replies to be sent from the wrong interface in contrived configurations.
Starting with Recursor 3.7.1, 0.0.0.0 even works in those contrived
setups, on kernels that allow us to extract the relevant metadata on an
incoming UDP query.
Kind regards,
--
Peter van Dijk
PowerDNS.COM BV - https://www.powerdns.com/
On 7 Nov 2015, at 16:26, Rob Locke wrote:
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> wrote:
What is the syntax to specify that pdns_recursor listen on all
interfaces
(something like "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 <javascript:;>
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
_______________________________________________
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
