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

Nameserver MX not in results_technical in API #882

Closed
bwbroersma opened this issue Feb 23, 2023 · 0 comments · Fixed by #887
Closed

Nameserver MX not in results_technical in API #882

bwbroersma opened this issue Feb 23, 2023 · 0 comments · Fixed by #887
Assignees
@mxsasha
Labels
bug Unexpected or unwanted behaviour of current implementations
Milestone
v1.7

Comments

@bwbroersma
Copy link
Collaborator

I have the keys:
"domain",
"nameservers",
"receiving_mailservers",
"status",

I cannot find the NS of the MX.
@bwbroersma bwbroersma added this to the v1.7 milestone Feb 23, 2023
@baknu baknu added the bug Unexpected or unwanted behaviour of current implementations label Feb 23, 2023
mxsasha added a commit that referenced this issue Feb 27, 2023
@mxsasha
Fix #882 - Include mx_nameservers in results_technical
b1217e1
@mxsasha mxsasha linked a pull request Feb 27, 2023 that will close this issue
Fix #882 - Include mx_nameservers in results_technical #887
Merged
mxsasha added a commit that referenced this issue Feb 27, 2023
@mxsasha
Fix #882 - Include mx_nameservers in results_technical (#887)
d84a008
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mxsasha mxsasha

Labels
bug Unexpected or unwanted behaviour of current implementations
Milestone
v1.7
Development

Successfully merging a pull request may close this issue.

Fix #882 - Include mx_nameservers in results_technical internetstandards/Internet.nl
3 participants
@mxsasha @bwbroersma @baknu