Adding two IP addresses for one host

Klinkefus, David S DSKlinkefus at midamerican.com
Fri Aug 31 19:16:45 UTC 2001


I would do it this way ----
Setup the new server as a secondary of the original server. After that
then set the workstations up to point to the secondary for DNS. When you
turn
down the original primary, then the workstations will already have the
information
about the new server. Change your records to reflect the 'new' primary, and
then
update the records in your server to show the new information. Then make the

changes necessary with Network Solutions.

Good Luck!

Dave K.

-----Original Message-----
From: erik at rmwt.net [mailto:erik at rmwt.net]
Sent: Friday, August 31, 2001 1:05 PM
To: comp-protocols-dns-bind at moderators.isc.org
Subject: Adding two IP addresses for one host



We have some servers that will be moving soon, so that we don't have
to update all the DNS records when it moves, we would like to put in
two IP records for te same host so that when the first one quits
working, the second will take over.  The Oreilly BIND book indicates
that if you simply put in 2 IP's it is a round robin thus there is no
guarantee that the correct host will be found.  Is there a better way
to do this to ensure they hit the server?  Something along the same
line as doing two different MX records and making one a 10 record, the
next a 20 record, etc??

as an example, here is what I am talking about, but from the book,
this will not work that the domain always resolves to the "working"
domain.

server.ourdomain.net   IN A    192.168.225.8
server.ourdomain.net   IN A    192.168.127.5

(These IP's are obviously just examples, we are using a routable class
C)




More information about the bind-users mailing list