Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warning: Failed to lookup DMARC even when Organizational domain policy found #1478

Open
reevesjeremy opened this issue Dec 18, 2024 · 1 comment
Labels
public-reported This issue is reported by the public users of the tool.

Comments

@reevesjeremy
Copy link

Subdomains that dont have their own DMARC policy record automatically inherit the DMARC policy from its parent. exo is already handling that lookup, but is also throwing "Failed to resolve" warnings

I think before the the DMARC function logs a lookup failure, it should chase the domain tree to find if a record is published for a parent domain, and only throw the Failed to resolve warning if there is also no parent DMARC policy. Otherwise the warning is distracting and misleading.

@buidav buidav added the public-reported This issue is reported by the public users of the tool. label Dec 19, 2024
@adhilto
Copy link
Collaborator

adhilto commented Dec 19, 2024

Thanks again for this report. I've opened #1479 to track the underlying issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
public-reported This issue is reported by the public users of the tool.
Projects
None yet
Development

No branches or pull requests

3 participants