[TriLUG] DIG and Nameservers

[Aaron Joyner via TriLUG]

Yeah, the wildcard (as pointed out by other-Aaron) seems to have been your
problem.  I misdiagnosed the common _spf.<domain> mistake, but I'm glad you
got to the bottom of it anyway.  :)

On Fri, Feb 17, 2017 at 4:35 PM, Brian McCullough <bdmc at bdmcc-us.com> wrote:

> On Fri, Feb 17, 2017 at 04:35:32PM -0500, Aaron S. Joyner wrote:
> > First, don't trust whois.  You're on the right track using dig.  Try "dig
> > +trace rentalventures.com" to see how a standard resolver walks the set
> of
> > NS authority records from the root nameservers down to the domain in
> > question.
>
> Thank you for the usual very informative answer.
>
> Actually, both MX records have been there for a long time, but I suspect
> that the following was causing the second to not be seen.
>
> They were "rentalventures.com MX 5 whatever" and "*.rentalventures.com
> MX 25 whatever".
>
> When I changed the priorities, I also removed the "*".
>
> Thank you for the explanation about SPF ( TXT ) records.  I didn't know
> that.
>
>
> Thanks again, Aaron.  Long time no see.
>
>
> Brian
>
>
>