[166283] in North American Network Operators' Group
Re: Yahoo reporting "No MX or A Records" and bouncing emails
daemon@ATHENA.MIT.EDU (Matthew Petach)
Tue Oct 15 18:10:09 2013
In-Reply-To: <CAC47Z9k=WrXXFahPxq5Z9SbUXCBK1y1z9XMbmUXTJOF_EsBL=w@mail.gmail.com>
Date: Tue, 15 Oct 2013 15:07:59 -0700
From: Matthew Petach <mpetach@netflight.com>
To: Jonathan Rogers <quantumfoam@gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
A really good first step is to indicate what domain is
having problems, so people can double-check to
make sure there's nothing unusual or broken
seen from other parts of the network, and if
necessary, escalate the issues with private
contacts.
I'm assuming it's not for the domain you're
sending your email from, in this case; but
if that's a bad assumption, please let
me know.
Thanks!
Matt
On Tue, Oct 15, 2013 at 1:18 PM, Jonathan Rogers <quantumfoam@gmail.com>wrote:
> DNSSEC does not appear to be set up on our name servers (which is where
> their DNS is), but this has never been an issue before. In searching the
> web about this specific message all I am finding is people saying:
>
> 1. Yahoo refuses to acknowledge or fix this, and it is happening to a lot
> of random people
> 2. Get email other than Yahoo (which isn't really helpful and I can't
> exactly tell my client that)
>
> How do I get a real person at Yahoo?
>
> Thanks,
>
> Jonathan Rogers
> PCM, Inc
>
>
> On Tue, Oct 15, 2013 at 4:05 PM, Jonathan Rogers <quantumfoam@gmail.com
> >wrote:
>
> > Rubens,
> >
> > Excellent point. I'm running an analysis on the domain in question now...
> >
> > Thanks,
> >
> > Jonathan Rogers
> > PCM, Inc
> >
> >
> > On Tue, Oct 15, 2013 at 4:00 PM, Rubens Kuhl <rubensk@gmail.com> wrote:
> >
> >>
> >>
> >>
> >> On Tue, Oct 15, 2013 at 4:56 PM, Jonathan Rogers <quantumfoam@gmail.com
> >wrote:
> >>
> >>> Greetings Programs,
> >>>
> >>> Yahoo is bouncing email that is being sent to a customer of mine with
> the
> >>> error that no MX or A records were found for the domain. There is
> nothing
> >>> wrong with the domain at all, which I have verified from multiple
> >>> sources.
> >>>
> >>> Does anyone have any suggestions about who I can reach out to at Yahoo
> to
> >>> get this matter resolved?
> >>>
> >>
> >> Multiple sources including DNSSEC-aware ones like dnsviz.net ? If the
> >> domain is failing DNSSEC, it would appear normal to conventional DNS
> tests.
> >>
> >> Rubens
> >>
> >>
> >
> >
>
>
