DNS is not the place to solve that problem, it's the routing layer. "Use Bgp Luke " :-)
Sent from my iPad On 08/05/2013, at 15:24, Sten Carlsen <st...@s-carlsen.dk> wrote: > I believe your major point is the routing tables because they determine how > the response is trying to get out. > > > On 08/05/13 22:22, Steven Carr wrote: >> 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 <mw...@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. >>> >>> ========================== >>> This email, and any files transmitted with it, is confidential and intended >>> solely for the use of the individual or entity to which it is addressed. If >>> you have received this email in error, please notify the system manager. >>> This message contains confidential information and is intended only for the >>> individual named. If you are not the named addressee, you should not >>> disseminate, distribute or copy this e-mail. Please notify the sender >>> immediately by e-mail if you have received this message by mistake and >>> delete this e-mail from your system. If you are not the intended recipient, >>> you are notified that disclosing, copying, distributing or taking any >>> action in reliance on the contents of this information is strictly >>> prohibited. >>> _______________________________________________ >>> Please visit https://lists.isc.org/mailman/listinfo/bind-users to >>> unsubscribe from this list >>> >>> bind-users mailing list >>> bind-users@lists.isc.org >>> https://lists.isc.org/mailman/listinfo/bind-users >> _______________________________________________ >> Please visit https://lists.isc.org/mailman/listinfo/bind-users to >> unsubscribe from this list >> >> bind-users mailing list >> bind-users@lists.isc.org >> https://lists.isc.org/mailman/listinfo/bind-users > > -- > Best regards > > Sten Carlsen > > No improvements come from shouting: > "MALE BOVINE MANURE!!!" > _______________________________________________ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe > from this list > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
