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
I encountered this issue when I had set the options
test case : gst.gov.in
var opts = {
"server": "whois.registry.in",
"follow": 3,
"verbose": true
}
the first lookup provided the results and did not contain any additional value in match[3]. Due to this , the values from servers.json was used . Incidentally, the value for "in" tld is incorrect.
In some cases match[3] is empty eg. match ["","","",""]
I encountered this issue when I had set the options
test case : gst.gov.in
var opts = {
"server": "whois.registry.in",
"follow": 3,
"verbose": true
}
the first lookup provided the results and did not contain any additional value in match[3]. Due to this , the values from servers.json was used . Incidentally, the value for "in" tld is incorrect.
In some cases match[3] is empty eg. match ["","","",""]
Solution :
index.js -->
if (match[3].trim().length == 0 ){
match[3] = options.server;
options.follow = 1;
}
PS: use dig tld.whois-servers.net CNAME to find the correct whoisServer in case servers.json has an incorrect value.
The text was updated successfully, but these errors were encountered: