"
Respectfully I disagree, if "Strict Interface Binding" doesn't really mean only the selected interfaces. Then it should either be stated clearly or really only bind to the defined interfaces. Dnsmasq isn't required to bind to 127 in order to function. It's clearly a maintainers choice they are choosing to make the default.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#2
18.7 Legacy Series / dnsmasq
January 22, 2019, 08:08:12 PM
I'm using OPNsense 18.7.10 how can I get dnsmasq to NOT bind to 127.X.X.X ? I've tried to checking the "Strict Interface Binding". But that doesn't really seem to be working ?
My end goal is to have dnsmasq listen on lan:53 (and wan:53 limited to X ips (firewall rules)) then have dnscrypt-proxy bind to 127.0.0.1:53
My end goal is to have dnsmasq listen on lan:53 (and wan:53 limited to X ips (firewall rules)) then have dnscrypt-proxy bind to 127.0.0.1:53
#4
General Discussion / Virtual IP
June 25, 2018, 09:39:33 PM
Is it possible to have a opnsense server fire off a script when it's status changes from backup to master and visa versa ?
I'm looking to have the backup server update a DNS record when it becomes the active gateway. It's not possible
for us to have x2 A records (for for each gateway). And we really only ever want the backup gateway to talked two if the "master" server goes down. (We acknowledge there will be a delay in DNS servers updating / distributing the new updated DNS records ).
I'm looking to have the backup server update a DNS record when it becomes the active gateway. It's not possible
for us to have x2 A records (for for each gateway). And we really only ever want the backup gateway to talked two if the "master" server goes down. (We acknowledge there will be a delay in DNS servers updating / distributing the new updated DNS records ).
Pages1
