Skip to content

[fix] HTTPS record type not resolved #10

Open
@Segmev

Description

@Segmev

Describe the bug

Node.js version: v22.14.0

OS version: Archlinux

Description: HTTPS record type not collected

Actual behavior

When fetching entries of HTTPS record type on any domain, resolve always throws ENODATA.

Expected behavior

To actually get valid HTTPS record entries.

Code to reproduce

resolve('google.com', 'HTTPS')

Throws:

Error: queryHttps ENODATA google.com
    at Tangerine.createError (...probe/node_modules/tangerine/index.js:349:17)
    at Tangerine.resolve (...probe/node_modules/tangerine/index.js:1779:30)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async Object.getDnsEntries (...probe/src/utils/dns.js:296:19) {
  hostname: 'google.com',
  syscall: 'queryHttps',
  code: 'ENODATA',
  errno: undefined

When testing with dohdec-cli, even on 5.0.3, we get:

[
  {
    name: 'google.com',
    type: 65,
    TTL: 21139,
    data: '\\# 13 00 01 00 00 01 00 06 02 68 32 02 68 33'
  }
]

Checklist

  • I have searched through GitHub issues for similar issues.
  • I have completely read through the README and documentation.
  • I have tested my code with the latest version of Node.js and this package and confirmed it is still not working.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions