On Sun, Aug 28, 2016, at 19:22, Paul Kosinski wrote:
> "... 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 th
"... 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 f
"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 -0400, Paul Kosin
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 interface
On Sat, Aug 27, 2016 at 02:32:42PM -0400, Paul Kosinski wrote:
> Currently, I forward all outbound DNS via the DSL to the ISP's
> DNS servers. (I have more confidence in the DSL provider not
> interfering with DNS than in Comcast.)
FWIW, it has been many years since I have dealt with Comcast as a
I have a rather unusual network with a gateway machine that connects to
two ISPs: a slower DSL with a static IP and a faster cable (Comcast)
with a DHCP IP. The gateway machine runs two instances of BIND (plus
the usual firewalling): an authoritative one for a couple of domains
(and only those doma
6 matches
Mail list logo
