We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This is mostly cosmetic, but we don't know what people depend on the ordering of the !j-* command.
!j-*
The order observed here:
hanna:~ job$ whois -h irrd01.ip.gin.ntt.net '!s-lc' A123 NTTCOM,INTERNAL,RADB,RIPE,RIPE-NONAUTH,ALTDB,BELL,LEVEL3,RGNET,APNIC,JPIRR,ARIN,BBOI,TC,AFRINIC,ARIN-WHOIS,RPKI,REGISTROBR C
should be used in the j- command
j-
hanna:~ job$ whois -h irrd01.ip.gin.ntt.net '!j-*' A275 AFRINIC:Y:- ALTDB:Y:48228-48363 APNIC:Y:- ARIN:Y:124539-127020 ARIN-WHOIS:N:- BBOI:Y:8580-8758 BELL:Y:- INTERNAL:Y:- JPIRR:Y:- LEVEL3:Y:788058-788397 NTTCOM:Y:1000597-1000905 RADB:Y:4056392-4064452 REGISTROBR:N:- RGNET:Y:- RIPE:Y:- RIPE-NONAUTH:Y:- RPKI:N:- TC:Y:18980-19087 C
The text was updated successfully, but these errors were encountered:
5940474
Note that when a specific source list is provided, we retain the source order in which it was queried. For example:
!jARIN,NTTCOM,APNIC A65 ARIN:Y:98854-127729 NTTCOM:Y:988873-1002668 APNIC:Y:98854-123078 C
That seemed to me like good behaviour. In other words, the fix only affects the order of '!j-*', on purpose.
Sorry, something went wrong.
mxsasha
No branches or pull requests
This is mostly cosmetic, but we don't know what people depend on the ordering of the
!j-*
command.The order observed here:
should be used in the
j-
commandThe text was updated successfully, but these errors were encountered: