Really wierd glitch in resolution

Kevin Darcy kcd at daimlerchrysler.com
Thu Feb 22 23:04:38 UTC 2001


Are you getting this message back from *your*own* machine, or from some
machine in the mass.edu mail infrastructure? This could be as simple as a
botched forwarding alias.

In any case, if the address is bouncing, why not just remove it from the
mailing list? Obviously it's not doing anything useful...


- Kevin

Duncan Hill wrote:

> This question is part mail based, part DNS based, but its the DNS
> thats throwing me.
>
> I manage several majordomo lists, and one in particular is giving me
> gripe.  A user with an address at hcc.mass.edu is subscribed to the
> list.  However, when I send a message to the list, I get back an error
> that the user @hoc.mass.edu cannot be delivered to, because
> hoc.mass.edu does not exist.  I have used dig several times on
> hoc.mass.edu, and only get back the SOA for mass.edu.
>
> Unfortunately, I cannot run dig on the mail list machine (getting the
> compiler on that AIX box to play nice is a nightmare), so I can't tell
> what it is actually seeing.
>
> Has anyone heard of this oddity before?
>
> Help!
>
> --
>
> Sapere aude
> My mind not only wanders, it sometimes leaves completely.





More information about the bind-users mailing list