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

Cannot resolve specific host #4

Closed
z64 opened this issue Jan 6, 2021 · 2 comments
Closed

Cannot resolve specific host #4

z64 opened this issue Jan 6, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@z64
Copy link

z64 commented Jan 6, 2021

I have run into an issue attempting to use durian to resolve api.cognitive.microsoft.com. stdlib and other utilities can access and interact with this host fine, so it appears to be some issue with durian.. or perhaps I've misconfigured something?

I'm not that knowledgeable about DNS, so your help is appreciated.
I have example you can try here that fails: https://git.sr.ht/~z64/durian-issue-4/tree

Output is:

got std socket: #<TCPSocket:0x7fa845b91d10>
Unhandled exception: Invalid host address (Socket::Error)
  from lib/durian/src/durian/resolver.cr:223:17 in 'get_tcp_socket!'
  from src/durian-issue-4.cr:19:7 in '__crystal_main'
  from ../../../../../usr/lib/crystal/crystal/main.cr:105:5 in 'main_user_code'
  from ../../../../../usr/lib/crystal/crystal/main.cr:91:7 in 'main'
  from ../../../../../usr/lib/crystal/crystal/main.cr:114:3 in 'main'
  from __libc_start_main
  from _start
  from ???
@636f7374 636f7374 added the bug Something isn't working label Jan 20, 2021
@636f7374
Copy link
Owner

636f7374 commented Jan 21, 2021

Reply

  • Thanks for your feedback, this problem will be fixed in the next Commit.
  • Due to some reasons, I did not receive the email reminder, so the processing progress was delayed (≈15 days).

636f7374 added a commit that referenced this issue Jan 21, 2021
Sometimes the Offset of the resource pointer exceeds 255, resulting in an error in the analysis. After two days of research, the problem has been fixed.
@z64
Copy link
Author

z64 commented Jan 21, 2021

@636f7374 I can confirm this fix works for us - thank you for fixing this & my other issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants