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
Linux btwiusearchvps 5.14.14-arch1-1 #1 SMP PREEMPT Wed, 20 Oct 2021 21:35:18 +0000 x86_64 GNU/Linux
Subsystem
dns.js
What steps will reproduce the bug?
Install NodeJS
Create a file, and paste the test code :
varInternalNodeDNS=require("dns");InternalNodeDNS.resolveAny("app.tabnine.com",(err,data)=>{if(err){// Error on the dns librarythrowerr;}console.log(data);});
I sadly do not have enough resource to test each NodeJS releases, so I just listed all that I tested in hope that it will help narrows down the issue.
This bug is currently impacting my custom private DNS server from being able to resolve any subdomains/domains, while I only have 1 test domain, I can't really 100% figure out if it's really just because of the underscore or not.
The app.tabnine.com are not my domain, I'm a tabnine user and was just confused on why I can't load up my tabnine account dashboard and my private DNS throws a lot of EBADRESP error.
The text was updated successfully, but these errors were encountered:
Probably the same as #39780. We’re attempting to update to the latest c-ares in #40660.
Mesteery
added
cares
Issues and PRs related to the c-ares dependency or the cares_wrap binding.
duplicate
Issues and PRs that are duplicates of other issues or PRs.
labels
Nov 1, 2021
Not at the moment. We're having some CI issues preventing anything from landing at the moment. Once it's merged into a 17 release we'd usually wait two weeks before releasing in LTS.
Version
v14.18.1 ( with other versions too.... )
Platform
Linux btwiusearchvps 5.14.14-arch1-1 #1 SMP PREEMPT Wed, 20 Oct 2021 21:35:18 +0000 x86_64 GNU/Linux
Subsystem
dns.js
What steps will reproduce the bug?
or an exception instead :
How often does it reproduce? Is there a required condition?
This issue will only happen with these conditions :
Based on tests I had done, the issue will happen on these NodeJS version :
While these NodeJS version won't produce the issue on my tests :
What is the expected behavior?
Responses with a correct DNS response data, not an exception.
I used
app.tabnine.com
as my test case DNS data.The result should be an :
which is an equivalent to the dig DNS lookup utility :
or the nslookup response :
What do you see instead?
An exception :
Additional information
From the exception message, it looks like that the inner exception was coming from this function :
Source :
NodeJS v16.9.0 dns.js lib
I sadly do not have enough resource to test each NodeJS releases, so I just listed all that I tested in hope that it will help narrows down the issue.
This bug is currently impacting my custom private DNS server from being able to resolve any subdomains/domains, while I only have 1 test domain, I can't really 100% figure out if it's really just because of the underscore or not.
The
app.tabnine.com
are not my domain, I'm a tabnine user and was just confused on why I can't load up my tabnine account dashboard and my private DNS throws a lot of EBADRESP error.The text was updated successfully, but these errors were encountered: