Hello,

Yes, this is Yahoo being special.  There are two MX records set up
correctly.

How long before this gets migrated to Verizon's back end?

Mitch

On Tue, May 9, 2017 at 9:13 PM Daryl Tester <
[email protected]> wrote:

>  Yeah, what Josh said.  RFC says fallback to A records if no MX
>  records are found, and your A record is set correctly (obviously,
>  otherwise it wouldn't work at all).
>
>  You stay special, Yahoo.
>
>  On Tue, 9 May 2017 09:01:09 -0700, John R. Hogerhuis wrote:
> > Kurt is getting this error when he sends to the list:
> >
> > ------------------------------------------------------------
> > ---------------------------------------------
> > Sorry, we were unable to deliver your message to the following
> > address.
> >
> > <[email protected]>:
> > No mx record found for domain=lists.bitchin100.com
> > ------------------------------------------------------------
> > ---------------------------------------------
> >
> > Seems to be Yahoo specific.
> >
> > Bitchin100 is hosted at DreamHost
> >
> > I'm not a DNS expert. Anyone know if there's a way I can resolve it
> > on my
> > end?
> >
> > -- John.
>
> --
>  Regards,
>    Daryl Tester
>    Handcrafted Computers Pty. Ltd.
>

Reply via email to