You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting from 13 July daily buildtest/internet/test-dns.js has been failing in node-test-commit-custom-suites-freestyle (test-internet) and on GH actions.
08:20:22 not ok 9 internet/test-dns08:20:22 ---08:20:22 duration_ms: 137.0810008:20:22 severity: fail08:20:22 exitcode: 108:20:22 stack: |-08:20:22 test_reverse_bogus08:20:22 test_resolve4_ttl08:20:22 looking up nodejs.org..08:20:22 test_resolve6_ttl08:20:22 nodejs.org = 104.20.22.46,104.20.23.4608:20:22 test_resolveMx08:20:22 test_resolveMx_failure08:20:22 test_resolveNs08:20:22 test_resolveNs_failure08:20:22 test_resolveSrv08:20:22 test_resolveSrv_failure08:20:22 test_resolvePtr08:20:22 test_resolvePtr_failure08:20:22 test_resolveNaptr08:20:22 test_resolveNaptr_failure08:20:22 test_resolveSoa08:20:22 test_resolveSoa_failure08:20:22 test_resolveCaa08:20:22 test_resolveCaa_failure08:20:22 test_resolveCname08:20:22 16 tests completed08:20:22 (node:14833) internal/test/binding: These APIs are for internal testing only. Do not use them.08:20:22 (Use `node --trace-warnings ...` to show where the warning was created)08:20:22 node:internal/errors:49608:20:22 ErrorCaptureStackTrace(err);08:20:22 ^08:20:22 08:20:22 Error: queryCname ENODATA blog.nodejs.org08:20:22 at QueryReqWrap.onresolve [as oncomplete] (node:internal/dns/promises:251:17) {08:20:22 errno: undefined,08:20:22 code: 'ENODATA',08:20:22 syscall: 'queryCname',08:20:22 hostname: 'blog.nodejs.org'08:20:22 }08:20:22 08:20:22 Node.js v21.0.0-pre08:20:22 ...
This was the next day after we added a CNAME entry for blog.nodejs.org: nodejs/build#3404 (comment)
Previously blog.nodejs.org was caught by the (now removed) CNAME entry for *.nodejs.org.
I ran a few dns.resolveCname() calls for the other CNAME entries we have and it looks like any of the proxied ones are also returning ENODATA but the non-proxied ones succeed. The previous *.nodejs.org CNAME entry was not proxied: nodejs/build#3404 (comment)
I've removed the proxy setting for blog.nodejs.org -- this didn't immediately fix the issue but trying on a different system worked and I've just tried again on the original system I was testing on and it now works so there's probably some DNS TTL caching going on.
Activity
richardlau commentedon Jul 21, 2023
I ran a few
dns.resolveCname()calls for the other CNAME entries we have and it looks like any of the proxied ones are also returningENODATAbut the non-proxied ones succeed. The previous*.nodejs.orgCNAME entry was not proxied: nodejs/build#3404 (comment)I've removed the proxy setting for
blog.nodejs.org-- this didn't immediately fix the issue but trying on a different system worked and I've just tried again on the original system I was testing on and it now works so there's probably some DNS TTL caching going on.CI: https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/31687/
richardlau commentedon Jul 21, 2023
test-dns.js passed 🎉. I'll open another issue for the
test-net-autoselectfamily-timeout-closefailure.