🚀 go-pugleaf

In article <walt-0810951720280001@walt.pr.mcs.net>,
Walt Pesch <walt@solgrp.chi.il.us> wrote:
>***  HELP PLEASE!!!  ***
>
>My ISP (MCS) has apparently changed their internal DNS structure and/or
>filtering this past week.  This has without warning broken my MX record
>which has for the last two years (after moving to MCS.COM after CLOUT left
>UofC) successfully resolved to Mercury.mcs.com.

We have changed *internal* machine functions, yes.  

The problem is the PROPER *MX* host for UUCP customers of MCSNet has ALWAYS
been either "uucphost.mcs.com" (historical) or "uucphost.mcs.net".  NO
OTHERS are guaranteed to work.

Mercury USED TO (over a year ago) handle UUCP.  It then moved to Mailbox,
sometime last year, which also handles user mail.  About a week ago (in 
conjunction with our other UUCP changes) it was put on a dedicated 
multiprocessor 133Mhz system to meet our promise of greatly improved 
UUCP performance and reliability.  

That promise has been kept.

The new machine is physically called "uucp1", and the CNAME pointers were 
changed internally to point UUCPHOST there.  90+% of our customers were
correctly configured (including those using UUCP over TCP/IP) and
experienced NO problems of this kind in the switch.  In fact, except for 
an "unavailable" period while disks were copied, those customers saw *no*
changes other than performance-related ones.

ISPs have *documented* names for machines for a REASON.  Using hard-coded
names you think do multiple things is a really bad idea, especially for
automatons such as mail forwarding (which doesn't know enough to "see" that
something is having a bad effect).

--
--
Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity
Modem: [+1 312 248-0900]     | (shell, PPP, SLIP, leased) in Chicagoland
Voice: [+1 312 803-MCS1]     | 7 Chicagoland POPs, ISDN, 28.8, much more
Fax: [+1 312 248-9865]       | Email to "info@mcs.net" WWW: http://www.mcs.net
ISDN - Get it here TODAY!    | Home of Chicago's *Three STAR A* Clarinet feed!