[54877] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: uunet

daemon@ATHENA.MIT.EDU (Tim Thorne)
Sun Jan 19 17:22:15 2003

From: tim.thorne@btinternet.com (Tim Thorne)
To: "Dave Howe" <DaveHowe@gmx.co.uk>
Cc: <nanog@merit.edu>
Date: Sun, 19 Jan 2003 22:26:16 GMT
In-Reply-To: <01de01c2c004$f871b980$01c8a8c0@davehowe>
Errors-To: owner-nanog-outgoing@merit.edu


"Dave Howe" <DaveHowe@gmx.co.uk> wrote:

>there then followed a short conversation that amounted to that - given =
that
>$mydomain was working fine, they would *not* look at the problem for
>$contractorsdomain unless $contractor contacted them about it.  I found
>postmaster@contractorsdomain worked fine, so managed to get *that* guy =
to
>get uunet to fix the problem (and it was literally a thirty second fix).

You can hardly expect an ISP to change an MX record on the opinion
(right or wrong) of a third party. It could be someone trying a little
social engineering. The customer or ISP could be in the middle of some
DNS changes. It could be someone talking out of their backside. This
kind of request for change needs to come through the proper channels
from the customer or their nominated point of contact.

TT

home help back first fref pref prev next nref lref last post