Actually in a real disaster, if it takes out the building the ONLY DNS server I
can reasonably expect to be available here is the one we run on z/OS
for DR. Why? Because our distributed systems folks have not ever, never once,
conducted a disaster recovery excercise. There is no facility here to
recover our windows infrastructure in a timely manner like we do with our
mainframe services. While I do not agree that this is wise, I do not control
things. So, we wil have a mainframe back within a couple days of declaring a
disaster, but windows? I wouldn't expect it for weeks.
Not my pig, Not my farm.
The hipersocket solution via /etc/hosts worked in testing, while there are
other more elegant solutions, this one at least will prevent the problem
that was encountered.
Thanks everoyne!
-J
Marcy Cortes <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port
<[email protected]>
To
[email protected]
cc
04/24/2007 03:00 PM
Subject
Re: DNS
and Disaster Recovery
Please respond to
Linux on 390 Port <[email protected]>
It doesn't seem to unreasonable to me that if you have a script always
runs at startup to throw something in there if you detect you are at DR
and it's not a real diaster :) (presumably in a real disaster you can
get to your real DNS servers James?).
We have similar kind of issues. We run our own in house DR systems, but
behind firewalls. Some of the things we talk to for a test are behind
the firewall with z/Linux but under a different DNS name and address.
Some things are outside with firewall rules allowing us to get to them
(i.e. other servers that do disaster recovery by just running in
multiple locations). Gets pretty tricky. We will probably do the bind9
implementation while doing the tests to save us lots of manual work; but
will probably still add that DNS server to resolv.conf while at test so
that the production copies never have a chance to see it accidentally
and I can keep it in non-test side of the firewall.
Marcy Cortes
"This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based on
this message or any information herein. If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message. Thank you for your cooperation."
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
David Boyes
Sent: Tuesday, April 24, 2007 11:43 AM
To: [email protected]
Subject: Re: [LINUX-390] DNS and Disaster Recovery
> DNS addresses go in /etc/resolv.conf.
> If it's just a matter of adding the name and address of your z/OS
host,
> why not add it to the local hosts file?
EEEEEWWWWWW!
This will bite you. Particularly if/when you have to change the official
address of some host you've stuck in a local hosts file. You'll
invariably miss one guest, or you'll forget it's there and spend all
kinds of time beating your head against the wall why an address change
didn't work.
Save what little hair we have left. Stamp out host files in our time!
--db
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
