DNS Lookups Failing After Updating to Latest Node 20 and 18 for IBM i
还没有人认领这个 Issue。
- 主要语言
- JavaScript
- 星标
- 122k
- 派生
- 37.4k
- 平均合并
- 4 天 3 小时
- 30 天内合并 PR
- 272
描述
Version
v20.15.1
Platform
IBM i 7.3:
OS400 idev 3 7 00780002A1F1 powerpc Os
Subsystem
DNS
What steps will reproduce the bug?
Any DNS lookup fails with connection timeout. Can run this code to reproduce:
require("dns").resolve("smtp.office365.com", function() { console.log(arguments); })
Fails with ETIMEOUT, even though the system DNS configuration is good and other software can perform DNS lookups.
How often does it reproduce? Is there a required condition?
Every time. This started happening when updating to Node 20.15.1 and Node 18.20.4 for IBM i. Everything was working fine before the update. Before, I was using Node 20.11.1 and Node 18.18.2.
What is the expected behavior? Why is that the expected behavior?
I expect a good DNS lookup, as the system DNS configuration is good and most other software can perform lookups.
What do you see instead?
ETIMEOUT on any DNS lookup.
Additional information
An interesting thing we noticed that may relate....
On the affected systems, the NSLOOKUP CL command can perform lookups with no problem, but the nslookup command in PASE fails with ETIMEOUT for any lookup.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
首先,在 IBM i 7.3 上使用 Node 20.15.1 或 18.20.4,通过 require("dns").resolve("smtp.office365.com", ... ) 重现该问题。将 PASE 中失败的 nslookup 行为与正常工作的 NSLOOKUP CL 命令以及之前正常工作的 Node 版本进行比较。完成的标准是:受影响的版本上的 DNS 查找不再超时,并且该回归问题由适当的测试覆盖。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- node.js
- 领域
- networking
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 42/100