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] Multihomed MX records are not handled correctly #17

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

[BUG] Multihomed MX records are not handled correctly #17

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

Comments

@AlexeyDemidov
Copy link

As the MX records are not resolved to IPs but used as is, it can lead to unexpected results during MX checks. For example, if MX record is multihomed and resolves into multiple A/AAAA records then there is some probability that check_port and run will run against different IPs.
@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 Multihomed MX records are not handled correctly [BUG] Multihomed MX records are not handled correctly 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