> On Oct 27, 2017, at 3:20 PM, Brandon Long <bl...@google.com> wrote:
>
> Isn't .us usually considered a 3 level tld, like .uk and .au? And DMARC says
> to ignore tlds.
Neustar decided second level domains were more valuable 15 years ago or so, and
it's mostly sold as a generic two level TLD now.
Given the history there are still a lot of three and four level hostnames in
there (states, .fed.us, .nsn.us, ...), and the weird
{ci,co,city,...}.<locality>.<state>.us stuff so it's probably one of the more
complex bits of organizational domain identification code.
Cheers,
Steve
>
> Brandon
>
>
> On Fri, Oct 27, 2017 at 3:01 PM Steve Atkins via dmarc-discuss
> <dmarc-discuss@dmarc.org> wrote:
>
> > On Oct 27, 2017, at 2:08 PM, Tyler South via dmarc-discuss
> > <dmarc-discuss@dmarc.org> wrote:
> >
> > Hey everyone,
> >
> >
> > We’ve been trying to track down what could possibly be causing this issue.
> > Google nevers send an aggregate report for our .US domain.
> >
> >
> >
> > We get aggregate reports from AOL, Yahoo, and Outlook on occasion but have
> > yet to get a single report from Google.
> >
> >
> > We use this very same .US domain to receive DMARC reports, both aggregate
> > and forensic, for about ten other domains that we manage. Google sends us
> > aggregate reports about those domains every day.
> >
> >
> > So we do get aggregate reports from Google for other domains in which we
> > are setup as the rua.We just don't get them for our own domain.
> >
> >
> > The DMARC record for our domain is,
> > "v=DMARC1;rua=mailto:aggrepo...@xxxxx.us;ruf=mailto:forrepo...@xxxxx.us;
> > p=reject; fo=1; sp=none"
>
> p=reject and sp=none?
>
> >
> >
> > We have modified it several times in failed attempts to resolve this issue.
> > We tried changing the RUA to other domains and services such as
> > DMARCAnalyzer and we have pretty much tried everything as far as changing
> > tags in the DMARC record goes.
> >
> >
> > Here is a copy of a DMARC record for a domain that google DOES send reports
> > for to us,
> > "v=DMARC1;rua=mailto:aggrepo...@xxxxx.us;ruf=mailto:forrepo...@xxxxx.us;
> > p=reject; fo=1;"
> >
> >
> > We can’t figure out any pattern to this madness.
>
> It does sound like something at Google and something in your DMARC record may
> not be playing nice together. Do you get forensic reports for that domain?
>
> >
> >
> > I mentioned our domain being a .US TLD repeatedly because I’m almost
> > convinced there is a bug that has something to do with reports not being
> > generated for a .US TLD.
>
> You might get more useful advice if you share what the relevant domains are,
> so we can look up what DMARC records you're publishing (and maybe check logs
> for those domains).
>
> Cheers,
> Steve
> _______________________________________________
> dmarc-discuss mailing list
> dmarc-discuss@dmarc.org
> http://www.dmarc.org/mailman/listinfo/dmarc-discuss
>
> NOTE: Participating in this list means you agree to the DMARC Note Well terms
> (http://www.dmarc.org/note_well.html)
_______________________________________________
dmarc-discuss mailing list
dmarc-discuss@dmarc.org
http://www.dmarc.org/mailman/listinfo/dmarc-discuss
NOTE: Participating in this list means you agree to the DMARC Note Well terms
(http://www.dmarc.org/note_well.html)
