-
Notifications
You must be signed in to change notification settings - Fork 31k
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
dns.resolveTxt() with multiple strings #52053
Comments
tried to investigate by myself: this behavior is produced by ares_parse_txt_reply_ext function from cares library Version 1.20.1 (8 Oct 2023) - this version of cares works well going to dig deeper and possible report my finding to c-ares project |
So from the issue you opened in c-ares it sounds like they confirm that there was indeed what can be considered a breaking change. So probably the c-ares update was not a patch, but a semver major? |
Yes, exactly! Now the branches 18, 20, 21 are affected, tested on v18.20.1, v20.12.1, v21.7.2 |
the current status:
|
Is this is resolved on the main branch, this issue can be closed. |
node v20.17.0, v22.5.0 - fixed affected node versions by this issue: |
Version
21.7.0
Platform
Linux server 4.18.0-477.27.1.el8_8.x86_64 #1 SMP Thu Aug 31 10:29:22 EDT 2023 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
dns
What steps will reproduce the bug?
dns records in somedomain
test IN TXT 0 string0
test IN TXT 1 string1
the code
import dns from "node:dns/promises"
let t = await dns.resolveTxt("test.somedomain")
console.dir(t)
How often does it reproduce? Is there a required condition?
always
What is the expected behavior? Why is that the expected behavior?
node versions before 21.7.0 return
[ [ '0', 'string0' ], [ '1', 'string1' ] ]
suppose this is the expected behavior
What do you see instead?
versions 21.7.0 and 21.7.1 return
[ [ '0string0' ], [ '1string1' ] ]
looks wrong
Additional information
No response
The text was updated successfully, but these errors were encountered: