-
# Explanation
When performing a WHOIS lookup using the `whois.lookup()` function on an IPv6 address (e.g., `2001:4860:4860::8888`), the response is returning `No match found.` However, when exec…
-
-
### Issue description
Now that we have the whois feature, when someone goes to get.gov/domains/choosing and enters a domain name, they could be accidentally entering it on the wrong page. For users…
-
```
"nodes": [
{
"id": "n0",
-
Firstly, whois function should send the WHOIS query with two arguments both being the nick, because to guarantee returning of idle time some servers need that. There are IRC clients which do this auto…
-
whois 2.7.0 returns different results when I try to lookup zhs389.com
while node-whois 2.…
-
When I use whois-json and I use NPM:
> ERROR in ./node_modules/whois/index.js 1:0
Module parse failed: Unexpected character '#' (1:0)
You may need an appropriate loader to handle this file type.
…
-
**Description**
When in a Docker swarm with swarm scoped macvlan networks, a stack fails to initialise upon docker reload
**Steps to reproduce the issue:**
1. Setup a docker swarm, on each host…
-
Is this intentional?
Every field is being concat'd rather than a separate entry. This only occurs when there is no recursive query (the query to whois.arin.net resolves without asking another serv…
-
### ⚠️ Please verify that this feature request has NOT been suggested before.
- [X] I checked and didn't find similar feature request
### 🏷️ Feature Request Type
New Monitor
### 🔖 Feature descript…