Skip to content

No DNS Search Domain support in C-Ares calls #17850

@Mickael-van-der-Beek

Description

@Mickael-van-der-Beek
  • Version: node:9.2.0-slim (Docker image)
  • Platform: Linux 8f48fe466727 4.9.49-moby 1 SMP Fri Dec 8 13:40:02 UTC 2017 x86_64 GNU/Linux
  • Subsystem: dns

It would seem that currently, Node.js calls through the C-Ares DNS resolver (resolve4() and resolve6()) don't support search domains.

Is this a bug? If not, are there current or planned configuration options to specify them?
Should this issue be cross-posted to the C-Ares repository?

To make reproduction of this issue easier, I created a Docker-based repository that you can find here:

https://github.com/Mickael-van-der-Beek/node-dns-test

PS: Be careful to not use Alpine Linux as Docker based image due to muslc being used and not glibc. I will create a ticket about this in their repository later.

EDIT: Might be related to this issue that was supposedly fixed in the past: #9799

Metadata

Metadata

Assignees

No one assigned

    Labels

    c++Issues and PRs that require attention from people who are familiar with C++.caresIssues and PRs related to the c-ares dependency or the cares_wrap binding.dnsIssues and PRs related to the dns subsystem.feature requestIssues that request new features to be added to Node.js.stale

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions