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.

Sign up for GitHub

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

Jump to bottom

[BUG] MX checks don't check if results are resolvable into A or AAAA records #12

Closed
AlexeyDemidov opened this issue Mar 25, 2019 · 1 comment
Closed

[BUG] MX checks don't check if results are resolvable into A or AAAA records #12

AlexeyDemidov opened this issue Mar 25, 2019 · 1 comment
Assignees
@bestwebua
Labels
bug Something isn't working

Comments

@AlexeyDemidov
Copy link

When MX records are found they should be resolved too and each MX should resolve into at least one A or AAAA record. If there is no A or AAAA records found for all MX records then MX checks should fail. See RFC 5321 Section 5 for details.
@bestwebua bestwebua self-assigned this Mar 28, 2019
@bestwebua bestwebua added the bug Something isn't working label Mar 28, 2019
@bestwebua bestwebua mentioned this issue Mar 30, 2019
Merged
7 tasks
bestwebua added a commit that referenced this issue Apr 1, 2019
@bestwebua
Fix mx issues: #10, #11, #12, #13, #17 (#22)
7bf5f37 
Implement MX lookup
Implement .valid? helper
Implement Configuration#retry_count
Implement ResolverExecutionWrapper
Update documentation
Update gem version
@bestwebua
Copy link
Member

Thank you, Alexey 👍 Fixed!

@bestwebua bestwebua changed the title MX checks don't check if results are resolvable into A or AAAA records [BUG] MX checks don't check if results are resolvable into A or AAAA records Nov 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bestwebua bestwebua

Labels
bug Something isn't working
Milestone
No milestone
Development

No branches or pull requests
2 participants
@AlexeyDemidov @bestwebua