The original question was worded too vaguely, sorry.
How can I automate a failover to a secondary NIC in my DU3.2g AlphaServer?
How can I setup DNS to failover to a different DNS if I have to failover to a
secondary NIC in my server?
What I really mean is;
I have two network interfaces in my DU3.2g machine. Each with it's own IP
Address.
I have configured each to have the same ip name.
I would like the machine to do every thing through one card (tu0) until that
card or the network
that tu0 is attached to dies. At the time that the system gets failures or
that one of our
monitoring systems notices the problem I would like to kick off a script that
set the DU box to use
tu1 for everything instead.
Is this possible?
Has anyone done it or something like it?
I guess I would need to route flush to get the system to figure out new
routes. What else?
Thank you.
The following are the responses to my first question.
Brian C. Hill bchill_at_ucdavis.edu wrote:
A second route might work for outgoing connections. For
incoming connections, some programs, like many telnets, will try each
address returned for a particular hostname. The twist with DNS is that
multiple RR's (resoucre records) in many of the newer named builds will
be returned in round-robin format - like a box of chocolates - you
never know what you are going to get. This is good in a way, because
repeated attempts should get you connected through the second card.
Julin Rodrguez wrote:
TruCluster software for Alpha on UNIX does it for you easily.
Robert L. McMillin wrote:
DNS fails over on the client side; that's why you have multiple 'server'
entries in your /etc/resolv.conf. Or am I not understanding what you
want to do?
Received on Fri Sep 19 1997 - 00:43:00 NZST