[THIN] Re: OT: DNS Toys
- From: "Taylor, George" <GTaylor@xxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Thu, 13 Jul 2006 16:09:35 -0600
The core IP scheme is changing also, going from 128.x.x.x to 10.x.x.x.
I do agree there are ways to make it easier, but the guys with the
mahagoney desks don't want to go that way.
George Taylor
Systems Programmer
Regional Health inc.
-----Original Message-----
From: Adam.Baum@xxxxxxxxxxxxxx [mailto:Adam.Baum@xxxxxxxxxxxxxx]
Sent: Thursday, July 13, 2006 4:01 PM
To: thin@xxxxxxxxxxxxx
Cc: thin@xxxxxxxxxxxxx; thin-bounce@xxxxxxxxxxxxx
Subject: [THIN] Re: OT: DNS Toys
How about giving the new server the old system's IP address when you
shut the old system down? If you have to bring up the old server,
either power off the new one or give it a different IP.
adam
"Roger Riggins"
<roger.riggins@ls
iowa.org>
To
Sent by: <thin@xxxxxxxxxxxxx>
thin-bounce@freel
cc
ists.org
Subject
[THIN] Re: OT: DNS Toys
07/13/2006 02:53
PM
Please respond to
thin@xxxxxxxxxxxx
g
You could just run a sniffer against that IP for all DNS traffic.
Good luck,
Roger Riggins
Network Administrator
Lutheran Services in Iowa
w: 319.859.3543
c: 319.290.5687
http://www.lsiowa.org
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]
On
Behalf Of Taylor, George
Sent: Thursday, July 13, 2006 4:21 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] OT: DNS Toys
I know this is way off topic, but there is so much brain power and
experience here I thought someone might know of something. We're
planning for an AD upgrade, 2000 to 2003, which includes replacing
a
few of our core DCs. One being replaced is the primary DNS server
for AD, basically "everything" in our central site has it as the
primary and all other sites have it as the secondary and thier
local
DC as the primary. To have a warm fuzzy feeling the bosses don't
want to touch this DC/IP/Name, so we basically need to simply shut
it
down at the time we flip and be able to bring it right back up if
needed. Just FYI, all external DNS that we are the master for is
handled by a couple Linux machines in the DMZ, so they won't be
touched.
90% of the change to point to another server for DNS is obvious
and
fairly easy to do with most of it being DHCP or servers. But we
are
worried about things like BioMed device or printers and such that
are
out there that we don't really know about. Certianly don't want
to
break a BioMed device and kill somebody, that could make for a bad
day. :-O
What we are thinking right now is some type of logging software to
sit on this machine for a week or two and logged the IP of
anything
performing a DNS lookup through it. Does anyone have any idea of
how
to handle something like this?
Thanks Much,
George Taylor
Systems Programmer
Regional Health inc.
Lutheran Services in Iowa Confidentiality Notice
==================================================================
The information contained in this communication may be confidential, is
intended only for the use of the recipient(s) named above, and may be
legally privileged. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution,
or copying of this communication, or any of its contents, is strictly
prohibited. If you have received this communication in error, please
return it to the sender immediately and delete the original message and
any copy of it from your computer system. If you have any questions
concerning this message, please contact the sender.
************************************************
For Archives, RSS, to Unsubscribe, Subscribe or set Digest or Vacation
mode use the below link:
//www.freelists.org/list/thin
************************************************
************************************************
For Archives, RSS, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
//www.freelists.org/list/thin
************************************************
Other related posts:
