"... whatever else you use to failover from the primary to the
secondary would automatically ensure BIND resolves too."
That's the root of the problem: there is no automatic failover, and
providing one is a lot of work. I was hoping there was a simple BIND
config option so that BIND itself could
"Your better bet is surely to dump the forwarders and to do your own
recursion."
It doesn't solve the connectivity issue, but it sounds reasonable in
it's own right: I'll have to try it.
On Sat, 27 Aug 2016 14:32:09 -0500
/dev/rob0 wrote:
> On Sat, Aug 27, 2016 at 02:32:42PM
Lets say my domain is foxtrot.com and we have SPF records for the SMTP
servers on foxtrot.com. Now lets say I have decided I want to allow
alphazulu.com to send mail as foxtrot.I know how to add alphazulu.com to
the SPF but If I wanted to also use DomainKeys or DKIM to authenticate
alphazulu.com
On Sat, Aug 27, 2016, at 11:32, Paul Kosinski wrote:
> So my question is, is it possible to configure my forwarding BIND to
> have a primary and *secondary* path for sending out DNS queries? As far
> as I can tell, the "query-source address" option in named.conf only
> allows one outbound
4 matches
Mail list logo