BIND Configuration

[Lawrence K. Chen, P.Eng.]

That's kind of how we do our DR...

I have things scripted so that every update to our zone, results two versions of the zone file...the master server signs the first one and does its usual notifies, then the master signs the second and its scp'd to secondaries in another network.

In the event we lose our connectivity....we can direct the remote slave to take over with with the alternate signed zone file.  So that our main web presence will resolve to servers at our DR site.....which we don't yet have :)

----- Original Message -----
> You will need to have some form of automation in place to update the
> DNS zone to change the IP address which should now be accessed when
> one of the links goes down. You will also need to ensure you have a
> low TTL value on the records you want to update on link change so
> that
> the records are refreshed quickly.
> 
> 
> 
> On 8 May 2013 20:40, Ward, Mike S <mward at ssfcu.org> wrote:
> > Hello all, I was wondering if someone could me out.
> >
> > I am using Bind 9.2 on a Redhat Linux server. We have two ISPS on
> > separate networks Lets call them A and B. My Linux Server can
> > listen on A's Network as well as B's network.
> > I'm using fictitious IPs and names
> >
> >         A 111.111.111.1                  B 555.555.555.1
> >                                    Secondary A 111.111.222.1
> >
> >                                   Redhat & Bind
> >
> > Bind is listening on both IP addresses and we have a secondary
> > server at 111.111.222.1
> >
> >
> > If A the ISP has a backbone router problem how can I get people
> > trying to get to our web servers to use B's network? I have been
> > think of different ways to do this, but have come up empty.
> >
> > Our network is really simple I just want to be able to use diverse
> > ISPS in case we lose one we still have the other. Can anyone help
> > me out. Any help appreciated.
> >
> > Thanks.
> >