blu@millipore.com (Brian Utterback) (09/06/90)
A few months ago Millipore (registered domain millipore.com) acquired
BioImage (registered domain bioimage.com). Bioimage has now been connected
via leased line to Millipore's tcpip network. Neither company directly
connects to the Internet, Millipore's forwarder is UUNET and Bioimage's is
Sharkey at the University of Michigan. The problem is now that Bioimage
(the company) is a part of Millipore (the company) we need to merge the two
domains.
Luckily, there is no problem for most of the machines. The Bioimage domain was
never more than one machine, which is to say that user@bioimage.com was the
outerworld address. The rest of the machines are known as
user@host.millipore.com. So the problem is that we want the one machine
(known as Maize) to be addressable as both maize.millipore.com and bioimage.com.
There is a large customer base that mails to bioimage.com so that must remain
for the time being.
Further complicating the matter, we want to discontinue the connection with
sharkey, using UUNET exclusively.
So, what do we do?
--
Brian Utterback, Millipore Corporation, 75G Wiggins Ave., Bedford Ma. 01730
Work:617-275-9200x8245, Home:603-891-2536
INTERNET:: blu@millipore.millipore.com
UUCP:: {samsung,cg-atla,merk,wang,bu-tyng}!millipore!blucricket@hpcc01.HP.COM (Cricket Liu) (09/07/90)
A few months ago Millipore (registered domain millipore.com) acquired
BioImage (registered domain bioimage.com). Bioimage has now been
connected via leased line to Millipore's tcpip network. Neither
company directly connects to the Internet, Millipore's forwarder is
UUNET and Bioimage's is Sharkey at the University of Michigan. The
problem is now that Bioimage (the company) is a part of Millipore (the
company) we need to merge the two domains.
Luckily, there is no problem for most of the machines. The Bioimage
domain was never more than one machine, which is to say that
user@bioimage.com was the outerworld address. The rest of the machines
are known as user@host.millipore.com. So the problem is that we want
the one machine (known as Maize)
"We call it Maize," eh?
to be addressable as both maize.millipore.com and bioimage.com. There
is a large customer base that mails to bioimage.com so that must remain
for the time being.
Further complicating the matter, we want to discontinue the connection
with sharkey, using UUNET exclusively.
So, what do we do?
Well, for the time being, the main thing you want to do is to change
bioimage.com's MX record to point to uunet.uu.net. (Once you let UUNET
know that it'll be handling Bioimage's mail.) You have to go the MX route:
you can't make bioimage.com a CNAME (alias) record, because it already has
NS records attached. (I've never asked the NIC if they'd set up a
second-level domain as a CNAME. Anyone know if they would?)
Next, make sure that whatever's on the other end of the uunet.uu.net UUCP
connection (presumably something called "millipore.com", or that can handle
mail addressed to "<user>@millipore.com") knows about bioimage.com. The
easiest way to do that, if you're running nameservers internally and aren't
connected to the Internet, is to set up "bioimage.com" as an alias for
"maize.millipore.com".
That should do it for the short term. Over time, you'll probably want to
wean correspondents off of "bioimage.com". The CNAME record pointing to
"maize.millipore.com" should take care of most of that - a large proportion
of correspondents simply reply to messages. The rest is really a PR issue.
You're lucky that Bioimage had such a small domain. I once had to do this
with a much larger one.
cricket
hostmaster@hp.comdavid@twg.com (David S. Herron) (09/08/90)
In article <4500001@hpcc01.HP.COM> cricket@hpcc01.HP.COM (Cricket Liu) writes: [A lot of really good suggestions..] [I'll note that making MMDF respond to two different domain names on the same host is pretty easy.. Mostly just a matter of listing both of the names in the "local channel" table.] >That should do it for the short term. Over time, you'll probably want to >wean correspondents off of "bioimage.com". The CNAME record pointing to >"maize.millipore.com" should take care of most of that - a large proportion >of correspondents simply reply to messages. The rest is really a PR issue. There is a technique, which happens to be pretty trivial to do in MMDF, which would help in getting your correspondants weaned. You fix up your mailer so that it recognizes certain names and sends back mail to the sender. In MMDF this is done with the blockaddr channel. You tell it a list of either domain names or full user addresses (user@domain) and a text file containing the message to send. Whenever mail passes by for one of them It shuffles a message off to wherever.. You may remember the CSNET conversion a few years ago. This was the cause of all those nice letters everybody received telling 'em about the change. (For those who don't know: CSNET used to use ".csnet" as it's top level `domain' name, and a couple of years ago they pushed all their customers to switch to "real" domain names.) I *assume* a similar thing can be done with sendmail :-) >You're lucky that Bioimage had such a small domain. I once had to do this >with a much larger one. > >cricket > >hostmaster@hp.com heh.. I can imagine.. Apollo wasn't (isn't?) small. -- <- David Herron, an MMDF & WIN/MHS guy, <david@twg.com> <- Formerly: David Herron -- NonResident E-Mail Hack <david@ms.uky.edu> <- <- Sign me up for one "I survived Jaka's Story" T-shirt!