> I was wondering what people have done in a situation like this, and if > anyone could tell me what configuration file to change during startup of > Linux > (before tcp/ip starts) to define the DR DNS address, or if there was a > better solution to this proposal. I can very easily enable the detection > of > whether or not a disaster recovery/test recovery in process, but I'm not > sure what all needs to change to supply the correct IP address for DNS > services in this case.
Best (and simplest) solution is to create a dedicated Linux guest running bind9 as a caching name server, and configure /etc/resolv.conf in that guest to point to the "official" name servers. Configure all your other guests to consult the dedicated Linux guest via a 192.168 address on an internal-only guest LAN or VSWITCH (eg, no physical connection to the outside). This technique lets you modify the actual DNS servers in use in only one place (the caching name server guest), and the rest of the farm never has to worry about it. (If you're really feeling clever, set up the caching name server to get it's configuration data from DHCP, and then you never have to tweak it at all.) It also allows RACFLDAP to continue to function if there is an interruption in connectivity to the real name servers for some reason. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
