Re: WHOIS rejection from strange IP address

To: debian-user@lists.debian.org
Subject: Re: WHOIS rejection from strange IP address
From: Andy Smith <andy@strugglers.net>
Date: Mon, 2 Dec 2024 17:06:16 +0000
Message-id: <[🔎] Z03pCPgQ8QQzsK29@mail.bitfolk.com>
In-reply-to: <[🔎] 87a5de81wt.fsf@sugarbit.com>
References: <cb3fa964-1838-faae-08c7-9688db4259eb@wlcr.net> <CAO6YxPzgL0gHYLiH0asdaXC0dLV5W+Bx+Z0-KX2EMfT=9UMvWw@mail.gmail.com> <CAO6YxPy6wiiZDJKNEHQyKuk2ZE_V_dh_JJNekPE2quY=rOASqw@mail.gmail.com> <[🔎] 3a182b84-664a-8f48-18dc-6d040191d634@wlcr.net> <[🔎] 87a5de81wt.fsf@sugarbit.com>

Hi,

On Mon, Dec 02, 2024 at 10:50:26AM -0600, John Hasler wrote:
> It isn't Debian.  It's that netblock.  Try 191.97.36.54.

I suspect that works because you are asking a LACNIC whois server for an
IP in its own database, so it's not having to contact RIPE's whois,
where the rejection seems to be coming from.

> whois -r 191.96.36.54

That works for me on Debian 11, I assume because by disabling recursive
lookups the LACNIC server is not doing as many queries to RIPE.

I don't need -r on Debian 12 whois for that query.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Reply to:

References:
- Re: WHOIS rejection from strange IP address
  - From: "vince@wlcr.net" <vince@wlcr.net>
- Re: WHOIS rejection from strange IP address
  - From: John Hasler <john@sugarbit.com>

Prev by Date: Re: WHOIS rejection from strange IP address
Next by Date: Re: WHOIS rejection from strange IP address
Previous by thread: Re: WHOIS rejection from strange IP address
Next by thread: Re: WHOIS rejection from strange IP address
Index(es):
- Date
- Thread