whois server

[Randy Bush]

```
% host whois.geektools.com
Host whois.geektools.com not found: 3(NXDOMAIN)
```

i guess i missed the memo :(

randy

Re: whois server

[Tom Paseka via NANOG]

the memo:
https://web.archive.org/web/20230523204911/http://www.geektools.com/

On Thu, Jul 13, 2023 at 1:27 PM Randy Bush  wrote:

> ```
> % host whois.geektools.com
> Host whois.geektools.com not found: 3(NXDOMAIN)
> ```
>
> i guess i missed the memo :(
>
> randy
>

Re: whois server

[Randy Bush]

> the memo:
> https://web.archive.org/web/20230523204911/http://www.geektools.com/

404

Re: whois server

[Matt Corallo]

Loads for me and just has a "we're shutting down notice", copied below.

But, like they say, modern whois knows where to look, no need to use anything else, I think as long 
as you're not stuck trying to use macOS or something else shipping weird ancient un-updated unix tools.


Matt


geektools.com has shut down.

We started this service in 1998 as the first smart whois that would automatically query the correct 
server(s) to get the data you need. A lot has changed since then and it's time to move on. Most 
modern command line clients on *nix-like systems will select the appropriate whois server. Check 
your system's man page ("man whois" for those of you who don't know what a man page is). If you 
prefer to use a browser interface there are many sites that perform the same function and they're 
easy to find with your favorite search engine.


It's been a good run, and thanks for using this service over the years.

- the geektools team

On 7/13/23 4:01 PM, Randy Bush wrote:

the memo:
https://web.archive.org/web/20230523204911/http://www.geektools.com/


404

Re: whois server

[John Levine]

It appears that Matt Corallo  said:
>But, like they say, modern whois knows where to look, no need to use anything 
>else, I think as long 
>as you're not stuck trying to use macOS or something else shipping weird 
>ancient un-updated unix tools.

If you're inclined to roll your own, I keep a set of whois server
pointers at .whois.services.net so for example
aero.whois.services.net is a CNAME for the whois server for .aero. I
update it daily using a the info in the IANA database and a bunch of
kludges to fill in the gaps.

There's a similar set at .whois-servers.net which seems to be
less up to date.

R"s,
John

PS: Someday I'll do it for rDNS, too.

options for whois server

[Spurling, Shannon]

Anyone out there who has to run an whois or rWhois service know of a currently 
maintained server package or option?

Thanks

Mr. Shannon Spurling

shan...@more.net

Fwd: whois server features

[shawn wilson]

Is there a list of NIC (and other popular whois server) features (what
can be searched on) and what data they provide (and what title they
give it)?

A quick search yields:
http://www.ripe.net/ripe/docs/ripe-358
https://www.arin.net/resources/whoisrws/whois_diff.html
https://www.apnic.net/apnic-info/whois_search/using-whois/searching/query-options

(In declining order of information - I also couldn't find the info for
AFRINIC queries) I also couldn't find information on what fields they
have (and obviously how they map to one another). There are also a few
other whois servers around that I have no idea about:
https://www.opensource.apple.com/source/adv_cmds/adv_cmds-149/whois/whois.c

Re: whois server features

[Bill Woodcock]

> On Jan 7, 2015, at 10:38 AM, shawn wilson  wrote:
> 
> Is there a list of NIC (and other popular whois server) features (what
> can be searched on) and what data they provide (and what title they
> give it)?

Heh, heh, heh.  There are just about as many whois output formats as there are 
back-end data-stores.  Note that I say “data-stores” rather than databases.  
Some of them aren’t.  So when you say “title” I assume you’re referring to half 
of a key-value pair.  A concept some large whois sources don’t have.

So, you’re not running into a poorly-documented mystery, you’ve run afoul of 
one of the rotten armpits of the shub-Internet.

-Bill






signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: whois server features

[shawn wilson]

On Wed, Jan 7, 2015 at 1:53 PM, Bill Woodcock  wrote:
>
>> On Jan 7, 2015, at 10:38 AM, shawn wilson  wrote:
>>
>> Is there a list of NIC (and other popular whois server) features (what
>> can be searched on) and what data they provide (and what title they
>> give it)?
>
> Heh, heh, heh.  There are just about as many whois output formats as there 
> are back-end data-stores.  Note that I say “data-stores” rather than 
> databases.  Some of them aren’t.  So when you say “title” I assume you’re 
> referring to half of a key-value pair.  A concept some large whois sources 
> don’t have.
>

Yes, I'm referring to mapping between key names.

> So, you’re not running into a poorly-documented mystery, you’ve run afoul of 
> one of the rotten armpits of the shub-Internet.
>

So there's no consensus between NICs for the information they should
have in whois and what search mechanisms they should provide? I guess
what you're saying is that whois is just a protocol definition and
nothing else?

Re: whois server features

[Rubens Kuhl]

>
> > So, you’re not running into a poorly-documented mystery, you’ve run
> afoul of one of the rotten armpits of the shub-Internet.
> >
>
> So there's no consensus between NICs for the information they should
> have in whois and what search mechanisms they should provide? I guess
> what you're saying is that whois is just a protocol definition and
> nothing else?
>

Might not even qualify for "protocol definition", and RFC 3912 ACKs this:

https://tools.ietf.org/html/rfc3912


Rubens

Re: whois server features

[Bill Woodcock]

>> So, you’re not running into a poorly-documented mystery, you’ve run afoul of 
>> one of the rotten armpits of the shub-Internet.
>> 
> So there's no consensus between NICs for the information they should
> have in whois and what search mechanisms they should provide? I guess
> what you're saying is that whois is just a protocol definition and
> nothing else?

Correct.  It gets you a blob of text.  Sometimes, a blob is just a blob.  Other 
times, it contains what _appear_ to be key-value pairs, but are instead 
loosely-formatted text.  Other times, it contains textually-represented 
key-value pairs that are programmatically generated from an actual database, 
and can thus be re-imported into another database.  Depends what’s on the back 
end.

-Bill






signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: whois server features

[shawn wilson]

On Wed, Jan 7, 2015 at 3:07 PM, Bill Woodcock  wrote:
>>> So, you’re not running into a poorly-documented mystery, you’ve run afoul 
>>> of one of the rotten armpits of the shub-Internet.
>>>
>> So there's no consensus between NICs for the information they should
>> have in whois and what search mechanisms they should provide? I guess
>> what you're saying is that whois is just a protocol definition and
>> nothing else?
>
> Correct.  It gets you a blob of text.  Sometimes, a blob is just a blob.  
> Other times, it contains what _appear_ to be key-value pairs, but are instead 
> loosely-formatted text.  Other times, it contains textually-represented 
> key-value pairs that are programmatically generated from an actual database, 
> and can thus be re-imported into another database.  Depends what’s on the 
> back end.
>

This is not the response I was looking for (and reading the RFC makes
me feel even worse).

Is there a better mechanism for querying NICs for host/owner information?

Re: whois server features

[Rubens Kuhl]

> This is not the response I was looking for (and reading the RFC makes
> me feel even worse).
>
> Is there a better mechanism for querying NICs for host/owner information?
>

There will be, one day. And the start (although not the whole journey) will
be when this I-D follows the standard path all the way to STD:
http://tools.ietf.org/html/draft-ietf-weirds-rdap-query-18.html


Rubens

Re: whois server features

[shawn wilson]

On Wed, Jan 7, 2015 at 3:32 PM, anthony kasza  wrote:
> Scripting languages have modules that can parse many registrar whois
> formats. However, most are incomplete due to the plurality of output formats
> as stated above. I, and i suspect many others, wouls *love* to see a more
> concrete key value format drafted and enforced by ICANN.
>

Yes, that's what I was looking at. And that REST API looks nice...
Though from what I read (admittedly not the whole doc yet) I didn't
see it defined what type of data is returned, nor what data should be
expected, which would leave me in the same place. If I'm only getting
a blob back (that would be, I guess, internationalized at this point)
I've still got to loop through with a regex expecting some type of
key/value thing and concatenate data after a line break to the last
value (probably removing spaces since they try to format it pretty).

Re: whois server features

[Nick Hilliard]

On 07/01/2015 20:07, Bill Woodcock wrote:
> Correct.  It gets you a blob of text.  Sometimes, a blob is just a blob.
> Other times, it contains what _appear_ to be key-value pairs, but are
> instead loosely-formatted text.  Other times, it contains
> textually-represented key-value pairs that are programmatically
> generated from an actual database, and can thus be re-imported into
> another database.  Depends what’s on the back end.

If only we could create a committee to fix whois...

Nick

Re: whois server features

[joel jaeggli]

On 1/7/15 12:48 PM, Nick Hilliard wrote:
> On 07/01/2015 20:07, Bill Woodcock wrote:
>> Correct.  It gets you a blob of text.  Sometimes, a blob is just a blob.
>> Other times, it contains what _appear_ to be key-value pairs, but are
>> instead loosely-formatted text.  Other times, it contains
>> textually-represented key-value pairs that are programmatically
>> generated from an actual database, and can thus be re-imported into
>> another database.  Depends what’s on the back end.
> If only we could create a committee to fix whois...
wierd, I've heard that before someplace.
> Nick
>




signature.asc
Description: OpenPGP digital signature

Re: whois server features

[anthony kasza]

Scripting languages have modules that can parse many registrar whois
formats. However, most are incomplete due to the plurality of output
formats as stated above. I, and i suspect many others, wouls *love* to see
a more concrete key value format drafted and enforced by ICANN.

-AK
On Jan 7, 2015 12:26 PM, "Rubens Kuhl"  wrote:

> > This is not the response I was looking for (and reading the RFC makes
> > me feel even worse).
> >
> > Is there a better mechanism for querying NICs for host/owner information?
> >
>
> There will be, one day. And the start (although not the whole journey) will
> be when this I-D follows the standard path all the way to STD:
> http://tools.ietf.org/html/draft-ietf-weirds-rdap-query-18.html
>
>
> Rubens
>

Re: whois server features

[David Conrad]

Hi,

> Scripting languages have modules that can parse many registrar whois
> formats. However, most are incomplete due to the plurality of output
> formats as stated above. I, and i suspect many others, wouls *love* to see
> a more concrete key value format drafted and enforced by ICANN.

ICANN can only 'enforce' stuff on the contracted parties, namely the gTLDs.  
And, in fact, they do so in contractual agreements (if you want the gory 
details, see Specification 4 of 
http://newgtlds.icann.org/sites/default/files/agreements/agreement-approved-09jan14-en.htm
 for registries and 
https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en#whois 
for registrars).

ICANN can't 'enforce' anything on the ccTLDs or RIRs.

Regards,
-drc



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: whois server features

[George Michaelson]

CRISP is dead. RDAP is real. If people need to script, then RDAP is
workable JSON and for once, has converged on sensible stuff in both names
and numbers.

the whois "problem" is a formalism owned  by ICANN,  but as DRC pointed out
the WHOIS solution is dispersed.

RPSL lies to one side btw. I wish it was a defined RDAP type. It may be
work-in-progress but thats not clear.

On Thu, Jan 8, 2015 at 11:38 AM, David Conrad  wrote:

> Hi,
>
> > Scripting languages have modules that can parse many registrar whois
> > formats. However, most are incomplete due to the plurality of output
> > formats as stated above. I, and i suspect many others, wouls *love* to
> see
> > a more concrete key value format drafted and enforced by ICANN.
>
> ICANN can only 'enforce' stuff on the contracted parties, namely the
> gTLDs.  And, in fact, they do so in contractual agreements (if you want the
> gory details, see Specification 4 of
> http://newgtlds.icann.org/sites/default/files/agreements/agreement-approved-09jan14-en.htm
> for registries and
> https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en#whois
> for registrars).
>
> ICANN can't 'enforce' anything on the ccTLDs or RIRs.
>
> Regards,
> -drc
>
>

Re: whois server features

[John Levine]

>If only we could create a committee to fix whois...

Quite astonishingly, the IETF WEIRDS working group finished
successfully, and its documents will be published as RFCs when they
get through the editing queue in a month or two.  The protocol is
called RDAP, the queries are http, the results are json.

ARIN, APNIC, and RIPE have prototypes already that are a lot easier to
script than the text WHOIS.

RDAP is also supposed to work for domain name WHOIS, but the timeline
there is less clear.  ICANN has hired cnnic to do a freeware version
which we hope a lot of smaller registries will use.

R's,
John

Re: whois server features

[shawn wilson]

On Wed, Jan 7, 2015 at 10:22 PM, John Levine  wrote:

> ARIN, APNIC, and RIPE have prototypes already that are a lot easier to
> script than the text WHOIS.
>

Meaning the data structure is in place or they have a RDAP service up?
If so, is it publicly accessible?

Re: whois server features

[George Michaelson]

http://rdap.apnic.net/

redirects to a web page documenting service

http://rdap.apnic.net/ip shows a json error response

http://rdap.apnic.net/ip/203.119.0.0/24

shows the /24 record for 203.119.0.0/24

-G


On Thu, Jan 8, 2015 at 1:59 PM, shawn wilson  wrote:

> On Wed, Jan 7, 2015 at 10:22 PM, John Levine  wrote:
>
> > ARIN, APNIC, and RIPE have prototypes already that are a lot easier to
> > script than the text WHOIS.
> >
>
> Meaning the data structure is in place or they have a RDAP service up?
> If so, is it publicly accessible?
>

Re: whois server features

[John R. Levine]

ARIN, APNIC, and RIPE have prototypes already that are a lot easier to
script than the text WHOIS.


Meaning the data structure is in place or they have a RDAP service up?


Both.  ARIN's and RIPE's are based on early versions so the URLs and JSON 
aren't quite what RDAP says they should be yet.



If so, is it publicly accessible?


Google is your friend.

R's,
John

Re: whois server features

[shawn wilson]

On Wed, Jan 7, 2015 at 11:23 PM, John R. Levine  wrote:

> Google is your friend.
>

Woops, you're right

Re: whois server features

[Franck Martin]

On Jan 7, 2015, at 10:38 AM, shawn wilson  wrote:

> Is there a list of NIC (and other popular whois server) features (what
> can be searched on) and what data they provide (and what title they
> give it)?
> 
Your best bet today is http://sourceforge.net/projects/phpwhois/

and from http://phpwhois.cvs.sourceforge.net/viewvc/phpwhois/phpwhois/

You will see there are nearly as many data mappers as there are TLDs…

WEIRDS is supposed to fix the protocol, data presentation and the field names, 
but not what fields will be present (as I understand it).



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: whois server features

[shawn wilson]

On Jan 8, 2015 4:23 AM, "Franck Martin"  wrote:
>
>
> On Jan 7, 2015, at 10:38 AM, shawn wilson  wrote:
>
> > Is there a list of NIC (and other popular whois server) features (what
> > can be searched on) and what data they provide (and what title they
> > give it)?
> >
> Your best bet today is http://sourceforge.net/projects/phpwhois/
>
> and from http://phpwhois.cvs.sourceforge.net/viewvc/phpwhois/phpwhois/
>

Awesome thanks. That answers half of my original question (though this
route was much more insightful than I thought). I can run with that (php
isn't my language but the etl is pretty clear).

Re: whois server features

[Sadiq Saif]

On 1/8/2015 09:02, shawn wilson wrote:
> Awesome thanks. That answers half of my original question (though this
> route was much more insightful than I thought). I can run with that (php
> isn't my language but the etl is pretty clear).
> 

There is a Python module if that is more your thing:
https://pypi.python.org/pypi/pythonwhois

-- 
Sadiq Saif
https://staticsafe.ca

Re: options for whois server

[Niels Bakker]

* shan...@more.net (Spurling, Shannon) [Mon 12 Feb 2024, 20:06 CET]:
Anyone out there who has to run an whois or rWhois service know of a 
currently maintained server package or option?


https://github.com/irrdnet/irrd4


-- Niels.

More Godaddy DNS and whois server issues?

[Mark Keymer]

Hi,

So this started a little while ago but seems to be getting worse.

What I am seeing is dns servers over at godaddy not replying however I 
seem to be able to traceroute ok to them. Also I have started to see 
that the whois.godaddy.com servers also seem to be having issues as well 
with "Whois information is currently unavailable.  Please try again later."


Anyone else also seeing issues this morning? And able to confirm the 
issue is with godaddy?


Sincerely,

--
Mark Keymer

Re: More Godaddy DNS and whois server issues?

[Steve Atkins]

On Sep 4, 2014, at 9:22 AM, Mark Keymer  wrote:

> Hi,
> 
> So this started a little while ago but seems to be getting worse.
> 
> What I am seeing is dns servers over at godaddy not replying however I seem 
> to be able to traceroute ok to them. Also I have started to see that the 
> whois.godaddy.com servers also seem to be having issues as well with "Whois 
> information is currently unavailable.  Please try again later."
> 
> Anyone else also seeing issues this morning? And able to confirm the issue is 
> with godaddy?

I've seen reports of this for a week or so, with the symptoms looking like 
overly aggressive abuse / query rate handling - packets from networks 
containing busy resolvers being blocked.

Grapevine tells me that they don't think they're doing it intentionally (maybe 
they outsourced something and it broke?).

Cheers,
  Steve

Re: More Godaddy DNS and whois server issues?

[Rob McEwen]

On 9/4/2014 12:55 PM, Steve Atkins wrote:
> On Sep 4, 2014, at 9:22 AM, Mark Keymer  wrote:
>
>> > Hi,
>> > 
>> > So this started a little while ago but seems to be getting worse.
>> > 
>> > What I am seeing is dns servers over at godaddy not replying however I 
>> > seem to be able to traceroute ok to them. Also I have started to see that 
>> > the whois.godaddy.com servers also seem to be having issues as well with 
>> > "Whois information is currently unavailable.  Please try again later."
>> > 
>> > Anyone else also seeing issues this morning? And able to confirm the issue 
>> > is with godaddy?
> I've seen reports of this for a week or so, with the symptoms looking like 
> overly aggressive abuse / query rate handling - packets from networks 
> containing busy resolvers being blocked.
>
> Grapevine tells me that they don't think they're doing it intentionally 
> (maybe they outsourced something and it broke?).


a few hours ago... One of my MX gateway filtering clients (for the small
spam filtering portion of my business) was having trouble this morning
with their own users accessing webmail (hosted on their exchange
server), and I discovered that the "a" record was resolving from some
locations, but not from others.  The domain was using GoDaddy's
"domaincontrol.com" series of name servers. I thought that they might
have had wrong host names in their registrar records and I told my
client to contact Godaddy, verify that these were correct, and ask
Godaddy about possible timeout and/or "no answer" issues. I tried
querying the host name from one location (direct to Godaddy's DNS) and
I'd get an answer, then from another location (direct to Godaddy's DNS)
and I would get a seemingly endless timeout.

-- 
Rob McEwen
+1 (478) 475-9032

Re: More Godaddy DNS and whois server issues?

[staticsafe]

On 9/4/2014 12:22, Mark Keymer wrote:
> Hi,
> 
> So this started a little while ago but seems to be getting worse.
> 
> What I am seeing is dns servers over at godaddy not replying however I
> seem to be able to traceroute ok to them. Also I have started to see
> that the whois.godaddy.com servers also seem to be having issues as well
> with "Whois information is currently unavailable.  Please try again later."
> 
> Anyone else also seeing issues this morning? And able to confirm the
> issue is with godaddy?
> 
> Sincerely,
> 

Do you have any particular NSes and/or domains we can test with?

-- 
staticsafe
https://staticsafe.ca

Re: More Godaddy DNS and whois server issues?

[Mark Keymer]

Hi,

They all came back later and are good now. But next time if it happens I 
will send some of the NS servers and domains.


Sincerely,

Mark


On 9/4/2014 9:26 AM, staticsafe wrote:

On 9/4/2014 12:22, Mark Keymer wrote:

Hi,

So this started a little while ago but seems to be getting worse.

What I am seeing is dns servers over at godaddy not replying however I
seem to be able to traceroute ok to them. Also I have started to see
that the whois.godaddy.com servers also seem to be having issues as well
with "Whois information is currently unavailable.  Please try again later."

Anyone else also seeing issues this morning? And able to confirm the
issue is with godaddy?

Sincerely,


Do you have any particular NSes and/or domains we can test with?

Re: More Godaddy DNS and whois server issues?

[Mark Andrews]

In message <540892d1.9090...@staticsafe.ca>, staticsafe writes:
> On 9/4/2014 12:22, Mark Keymer wrote:
> > Hi,
> > 
> > So this started a little while ago but seems to be getting worse.
> > 
> > What I am seeing is dns servers over at godaddy not replying however I
> > seem to be able to traceroute ok to them. Also I have started to see
> > that the whois.godaddy.com servers also seem to be having issues as well
> > with "Whois information is currently unavailable.  Please try again later."
> > 
> > Anyone else also seeing issues this morning? And able to confirm the
> > issue is with godaddy?
> > 
> > Sincerely,
> > 
> 
> Do you have any particular NSes and/or domains we can test with?

The following nameservers for godaddy.com are currently down.  The
machines themselves are up as we can ping them.

godaddy.com. @2600:1403:a::43 (a8-67.akam.net.): dns=timeout edns=timeout 
edns1=timeout edns@512=timeout ednsopt=timeout edns1opt=timeout
godaddy.com. @2a02:26f0:67::41 (a20-65.akam.net.): dns=timeout edns=timeout 
edns1=timeout edns@512=timeout ednsopt=timeout edns1opt=timeout
godaddy.com. @2600:1401:1::42 (a6-66.akam.net.): dns=timeout edns=timeout 
edns1=timeout edns@512=timeout ednsopt=timeout edns1opt=timeout

The above was from EDNS compliance testing I am doing.  The report
is regenerated daily.

http://users.isc.org/~marka/alexa-report.html

- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org

Re: More Godaddy DNS and whois server issues?

[Jay Ashworth]

I have an ear to whisper in on this topic at GD. 

If you're still having trouble through today, Thursday, please reply 
on this thread (or, if you're on Outages@, preferably over on that thread),
with what, when, and how, and I will pass the hard data along.

If you've already posted details here, just confirm still a problem, and
I can harvest.

The majority of the trouble is layer 3 and above, as I understand it; 
ping/trace to the relevant servers is working on, generally?  If otherwise,
mention that as well, pse.

Cheers,
-- jra

- Original Message -
> From: "Mark Keymer" 
> To: nanog@nanog.org
> Sent: Thursday, September 4, 2014 12:22:41 PM
> Subject: More Godaddy DNS and whois server issues?
> Hi,
> 
> So this started a little while ago but seems to be getting worse.
> 
> What I am seeing is dns servers over at godaddy not replying however I
> seem to be able to traceroute ok to them. Also I have started to see
> that the whois.godaddy.com servers also seem to be having issues as
> well
> with "Whois information is currently unavailable. Please try again
> later."
> 
> Anyone else also seeing issues this morning? And able to confirm the
> issue is with godaddy?
> 
> Sincerely,
> 
> --
> Mark Keymer

-- 
Jay R. Ashworth  Baylink   j...@baylink.com
Designer The Things I Think   RFC 2100
Ashworth & Associates   http://www.bcp38.info  2000 Land Rover DII
St Petersburg FL USA  BCP38: Ask For It By Name!   +1 727 647 1274

Problems getting to Verisign's whois server on IPv6

[TR Shaw]

Anyone else having problems getting to Verisign's whois server on IPv6?

$ host com.whois-servers.net
com.whois-servers.net is an alias for whois.verisign-grs.com.
whois.verisign-grs.com has address 199.7.59.74
whois.verisign-grs.com has IPv6 address 2001:503:3227:1060::74

$ traceroute6 2001:503:3227:1060::74
traceroute6 to 2001:503:3227:1060::74 (2001:503:3227:1060::74) from 
2001:470:5:4ed:cabc:c8ff:fea1:560c, 64 hops max, 12 byte packets
 1  2001:470:5:4ed:226:bbff:fe6d:426e  0.311 ms  0.374 ms  0.260 ms
 2  ipv6oitc-1.tunnel.tserv12.mia1.ipv6.he.net  21.128 ms  21.052 ms  17.389 ms
 3  gige-g2-3.core1.mia1.he.net  20.055 ms  16.198 ms  22.699 ms
 4  10gigabitethernet4-3.core1.atl1.he.net  40.166 ms  33.887 ms  32.547 ms
 5  10gigabitethernet6-4.core1.ash1.he.net  49.821 ms  45.999 ms  52.751 ms
 6  2001:504:0:2::2641:1  47.197 ms  46.748 ms  47.289 ms
 7  xe-1-2-0.r1.bb-fo.chi2.vrsn.net  65.094 ms
xe-0-2-0.r2.bb-fo.chi2.vrsn.net  66.441 ms
xe-1-2-0.r1.bb-fo.chi2.vrsn.net  66.320 ms
 8  2001:503:3227:14ff::2  66.448 ms
2001:503:3227:13ff::2  101.761 ms  86.864 ms
 9  2001:503:3227:13ff::2  69.818 ms !P
2001:503:3227:14ff::2  69.311 ms !P
2001:503:3227:13ff::2  68.662 ms !P

Re: Problems getting to Verisign's whois server on IPv6

[Tony Tauber]

Path is not the same, but the last few replies similarly suggest
packet-filters (!X in my case vs. !P).
I can get to the whois port (TCP/43):

$ telnet -6 2001:503:3227:1060::74 whois
Trying 2001:503:3227:1060::74...
Connected to 2001:503:3227:1060::74.
Escape character is '^]'.

Can you?

Tony

On Tue, May 1, 2012 at 8:01 AM, TR Shaw  wrote:

> Anyone else having problems getting to Verisign's whois server on IPv6?
>
> $ host com.whois-servers.net
> com.whois-servers.net is an alias for whois.verisign-grs.com.
> whois.verisign-grs.com has address 199.7.59.74
> whois.verisign-grs.com has IPv6 address 2001:503:3227:1060::74
>
> $ traceroute6 2001:503:3227:1060::74
> traceroute6 to 2001:503:3227:1060::74 (2001:503:3227:1060::74) from
> 2001:470:5:4ed:cabc:c8ff:fea1:560c, 64 hops max, 12 byte packets
>  1  2001:470:5:4ed:226:bbff:fe6d:426e  0.311 ms  0.374 ms  0.260 ms
>  2  ipv6oitc-1.tunnel.tserv12.mia1.ipv6.he.net  21.128 ms  21.052 ms
>  17.389 ms
>  3  gige-g2-3.core1.mia1.he.net  20.055 ms  16.198 ms  22.699 ms
>  4  10gigabitethernet4-3.core1.atl1.he.net  40.166 ms  33.887 ms  32.547
> ms
>  5  10gigabitethernet6-4.core1.ash1.he.net  49.821 ms  45.999 ms  52.751
> ms
>  6  2001:504:0:2::2641:1  47.197 ms  46.748 ms  47.289 ms
>  7  xe-1-2-0.r1.bb-fo.chi2.vrsn.net  65.094 ms
>xe-0-2-0.r2.bb-fo.chi2.vrsn.net  66.441 ms
>xe-1-2-0.r1.bb-fo.chi2.vrsn.net  66.320 ms
>  8  2001:503:3227:14ff::2  66.448 ms
>2001:503:3227:13ff::2  101.761 ms  86.864 ms
>  9  2001:503:3227:13ff::2  69.818 ms !P
>2001:503:3227:14ff::2  69.311 ms !P
>2001:503:3227:13ff::2  68.662 ms !P
>
>
>

Re: Problems getting to Verisign's whois server on IPv6

[TR Shaw]

Nope sure can't

$  telnet -6 2001:503:3227:1060::74 whois
2001:503:3227:1060::74: nodename nor servname provided, or not known

Tom

On May 1, 2012, at 8:15 AM, Tony Tauber wrote:

> Path is not the same, but the last few replies similarly suggest 
> packet-filters (!X in my case vs. !P).
> I can get to the whois port (TCP/43):
> 
> $ telnet -6 2001:503:3227:1060::74 whois
> Trying 2001:503:3227:1060::74...
> Connected to 2001:503:3227:1060::74.
> Escape character is '^]'.
> 
> Can you?
> 
> Tony
> 
> On Tue, May 1, 2012 at 8:01 AM, TR Shaw  wrote:
> Anyone else having problems getting to Verisign's whois server on IPv6?
> 
> $ host com.whois-servers.net
> com.whois-servers.net is an alias for whois.verisign-grs.com.
> whois.verisign-grs.com has address 199.7.59.74
> whois.verisign-grs.com has IPv6 address 2001:503:3227:1060::74
> 
> $ traceroute6 2001:503:3227:1060::74
> traceroute6 to 2001:503:3227:1060::74 (2001:503:3227:1060::74) from 
> 2001:470:5:4ed:cabc:c8ff:fea1:560c, 64 hops max, 12 byte packets
>  1  2001:470:5:4ed:226:bbff:fe6d:426e  0.311 ms  0.374 ms  0.260 ms
>  2  ipv6oitc-1.tunnel.tserv12.mia1.ipv6.he.net  21.128 ms  21.052 ms  17.389 
> ms
>  3  gige-g2-3.core1.mia1.he.net  20.055 ms  16.198 ms  22.699 ms
>  4  10gigabitethernet4-3.core1.atl1.he.net  40.166 ms  33.887 ms  32.547 ms
>  5  10gigabitethernet6-4.core1.ash1.he.net  49.821 ms  45.999 ms  52.751 ms
>  6  2001:504:0:2::2641:1  47.197 ms  46.748 ms  47.289 ms
>  7  xe-1-2-0.r1.bb-fo.chi2.vrsn.net  65.094 ms
>xe-0-2-0.r2.bb-fo.chi2.vrsn.net  66.441 ms
>xe-1-2-0.r1.bb-fo.chi2.vrsn.net  66.320 ms
>  8  2001:503:3227:14ff::2  66.448 ms
>2001:503:3227:13ff::2  101.761 ms  86.864 ms
>  9  2001:503:3227:13ff::2  69.818 ms !P
>2001:503:3227:14ff::2  69.311 ms !P
>2001:503:3227:13ff::2  68.662 ms !P
> 
> 
> 

Re: Problems getting to Verisign's whois server on IPv6

[Jaap Akkerhuis]

Anyone else having problems getting to Verisign's whois server on IPv6?

whois -h 2001:503:ff39:1060::74 verisign-grs.com

works for me.

jaap

RE: Problems getting to Verisign's whois server on IPv6

[Mike Simkins]

Seems to work for me

mps31@lonsgnsu1:~$ telnet -6 2001:503:3227:1060::74 whois
Trying 2001:503:3227:1060::74...
Connected to 2001:503:3227:1060::74.
Escape character is '^]'.

mps31@lonsgnsu1:~$ whois -h 2001:503:3227:1060::74 =verisign.com

Whois Server Version 2.0

Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.

   Domain Name: VERISIGN.COM
   Registrar: NETWORK SOLUTIONS, LLC.
   Whois Server: whois.networksolutions.com
   Referral URL: http://www.networksolutions.com/en_US/
   Name Server: A2.NSTLD.COM
   Name Server: C2.NSTLD.NET
   Name Server: D2.NSTLD.NET
   Name Server: E2.NSTLD.NET
   Name Server: F2.NSTLD.COM
   Name Server: G2.NSTLD.COM
   Name Server: H2.NSTLD.NET
   Name Server: J2.NSTLD.NET
   Name Server: K2.NSTLD.NET
   Name Server: L2.NSTLD.COM
   Name Server: M2.NSTLD.NET
   Status: clientTransferProhibited
   Status: serverDeleteProhibited
   Status: serverTransferProhibited
   Status: serverUpdateProhibited
   Updated Date: 14-apr-2011
   Creation Date: 02-jun-1995
   Expiration Date: 01-jun-2012

>>> Last update of whois database: Tue, 01 May 2012 12:29:12 UTC <<<

Mike Simkins ▪ Senior Network Engineer , Operations Engineering ▪ SunGard
Availability Services ▪ 25 Canada Square, London E14 5LQ

-Original Message-
From: TR Shaw [mailto:ts...@oitc.com]
Sent: 01 May 2012 13:23
To: Tony Tauber
Cc: NANOG list
Subject: Re: Problems getting to Verisign's whois server on IPv6

Nope sure can't

$  telnet -6 2001:503:3227:1060::74 whois
2001:503:3227:1060::74: nodename nor servname provided, or not known

Tom

On May 1, 2012, at 8:15 AM, Tony Tauber wrote:

> Path is not the same, but the last few replies similarly suggest
> packet-filters (!X in my case vs. !P).
> I can get to the whois port (TCP/43):
>
> $ telnet -6 2001:503:3227:1060::74 whois Trying
> 2001:503:3227:1060::74...
> Connected to 2001:503:3227:1060::74.
> Escape character is '^]'.
>
> Can you?
>
> Tony
>
> On Tue, May 1, 2012 at 8:01 AM, TR Shaw  wrote:
> Anyone else having problems getting to Verisign's whois server on IPv6?
>
> $ host com.whois-servers.net
> com.whois-servers.net is an alias for whois.verisign-grs.com.
> whois.verisign-grs.com has address 199.7.59.74 whois.verisign-grs.com
> has IPv6 address 2001:503:3227:1060::74
>
> $ traceroute6 2001:503:3227:1060::74
> traceroute6 to 2001:503:3227:1060::74 (2001:503:3227:1060::74) from
> 2001:470:5:4ed:cabc:c8ff:fea1:560c, 64 hops max, 12 byte packets
>  1  2001:470:5:4ed:226:bbff:fe6d:426e  0.311 ms  0.374 ms  0.260 ms
>  2  ipv6oitc-1.tunnel.tserv12.mia1.ipv6.he.net  21.128 ms  21.052 ms
> 17.389 ms
>  3  gige-g2-3.core1.mia1.he.net  20.055 ms  16.198 ms  22.699 ms
>  4  10gigabitethernet4-3.core1.atl1.he.net  40.166 ms  33.887 ms
> 32.547 ms
>  5  10gigabitethernet6-4.core1.ash1.he.net  49.821 ms  45.999 ms
> 52.751 ms
>  6  2001:504:0:2::2641:1  47.197 ms  46.748 ms  47.289 ms
>  7  xe-1-2-0.r1.bb-fo.chi2.vrsn.net  65.094 ms
>xe-0-2-0.r2.bb-fo.chi2.vrsn.net  66.441 ms
>xe-1-2-0.r1.bb-fo.chi2.vrsn.net  66.320 ms
>  8  2001:503:3227:14ff::2  66.448 ms
>2001:503:3227:13ff::2  101.761 ms  86.864 ms
>  9  2001:503:3227:13ff::2  69.818 ms !P
>2001:503:3227:14ff::2  69.311 ms !P
>2001:503:3227:13ff::2  68.662 ms !P
>
>
>

Re: Problems getting to Verisign's whois server on IPv6

[Jared Mauch]

This looks to be more of an application issue for you.

The rest seems to work for me:

puck:~$ whois -h 2001:503:ff39:1060::74 verisign-grs.com
[Querying 2001:503:ff39:1060::74]
[2001:503:ff39:1060::74]

Whois Server Version 2.0

...

- Jared

On May 1, 2012, at 8:23 AM, TR Shaw wrote:

> Nope sure can't
> 
> $  telnet -6 2001:503:3227:1060::74 whois
> 2001:503:3227:1060::74: nodename nor servname provided, or not known
> 
> Tom
> 
> On May 1, 2012, at 8:15 AM, Tony Tauber wrote:
> 
>> Path is not the same, but the last few replies similarly suggest 
>> packet-filters (!X in my case vs. !P).
>> I can get to the whois port (TCP/43):
>> 
>> $ telnet -6 2001:503:3227:1060::74 whois
>> Trying 2001:503:3227:1060::74...
>> Connected to 2001:503:3227:1060::74.
>> Escape character is '^]'.
>> 
>> Can you?
>> 
>> Tony
>> 
>> On Tue, May 1, 2012 at 8:01 AM, TR Shaw  wrote:
>> Anyone else having problems getting to Verisign's whois server on IPv6?
>> 
>> $ host com.whois-servers.net
>> com.whois-servers.net is an alias for whois.verisign-grs.com.
>> whois.verisign-grs.com has address 199.7.59.74
>> whois.verisign-grs.com has IPv6 address 2001:503:3227:1060::74
>> 
>> $ traceroute6 2001:503:3227:1060::74
>> traceroute6 to 2001:503:3227:1060::74 (2001:503:3227:1060::74) from 
>> 2001:470:5:4ed:cabc:c8ff:fea1:560c, 64 hops max, 12 byte packets
>> 1  2001:470:5:4ed:226:bbff:fe6d:426e  0.311 ms  0.374 ms  0.260 ms
>> 2  ipv6oitc-1.tunnel.tserv12.mia1.ipv6.he.net  21.128 ms  21.052 ms  17.389 
>> ms
>> 3  gige-g2-3.core1.mia1.he.net  20.055 ms  16.198 ms  22.699 ms
>> 4  10gigabitethernet4-3.core1.atl1.he.net  40.166 ms  33.887 ms  32.547 ms
>> 5  10gigabitethernet6-4.core1.ash1.he.net  49.821 ms  45.999 ms  52.751 ms
>> 6  2001:504:0:2::2641:1  47.197 ms  46.748 ms  47.289 ms
>> 7  xe-1-2-0.r1.bb-fo.chi2.vrsn.net  65.094 ms
>>   xe-0-2-0.r2.bb-fo.chi2.vrsn.net  66.441 ms
>>   xe-1-2-0.r1.bb-fo.chi2.vrsn.net  66.320 ms
>> 8  2001:503:3227:14ff::2  66.448 ms
>>   2001:503:3227:13ff::2  101.761 ms  86.864 ms
>> 9  2001:503:3227:13ff::2  69.818 ms !P
>>   2001:503:3227:14ff::2  69.311 ms !P
>>   2001:503:3227:13ff::2  68.662 ms !P
>> 
>> 
>> 
> 

Re: Problems getting to Verisign's whois server on IPv6

[Teun Vink]

On Tue, 2012-05-01 at 08:01 -0400, TR Shaw wrote:
> Anyone else having problems getting to Verisign's whois server on IPv6?
> 

Testing it using the NLNOG ring (https://ring.nlnog.net) shows that 3
nodes have routing issues, 92 have no problems reaching Verisign's whois
server on IPv6. So there might be some routing issues.

Here's a (tad too crowded) graph showing the traceroutes from all ring
nodes: https://ring.nlnog.net/paste/p/pqux9kxpzhytnnmx

Regards,
Teun

Re: Problems getting to Verisign's whois server on IPv6

[Christopher Morrow]

On Tue, May 1, 2012 at 8:59 AM, Teun Vink  wrote:
> On Tue, 2012-05-01 at 08:01 -0400, TR Shaw wrote:
>> Anyone else having problems getting to Verisign's whois server on IPv6?
>>
>
> Testing it using the NLNOG ring (https://ring.nlnog.net) shows that 3
> nodes have routing issues, 92 have no problems reaching Verisign's whois
> server on IPv6. So there might be some routing issues.
>
> Here's a (tad too crowded) graph showing the traceroutes from all ring
> nodes: https://ring.nlnog.net/paste/p/pqux9kxpzhytnnmx

mtu problems perhaps? (I get a connect, but nothing after the initial banner ...

-chris

Re: Problems getting to Verisign's whois server on IPv6

[Mark Andrews]

The server doesn't do PMTUD properly.   Verisign were informed of this
a while back.  How hard is it to let ICMPv6 PTB in so that PMTUD works?

% whois -h 2001:503:3227:1060::74 example.com

Whois Server Version 2.0

Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.
[stalls here forever]

The message is sent in 3 packet and you see packet 1 and 3, 2 is
lost and despite selective acks it is never seen.
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org

Re: Problems getting to Verisign's whois server on IPv6

[Christopher Morrow]

On Tue, May 1, 2012 at 7:25 PM, Mark Andrews  wrote:
>
> The server doesn't do PMTUD properly.   Verisign were informed of this
> a while back.  How hard is it to let ICMPv6 PTB in so that PMTUD works?
>
> % whois -h 2001:503:3227:1060::74 example.com
>
> Whois Server Version 2.0
>
> Domain names in the .com and .net domains can now be registered
> with many different competing registrars. Go to http://www.internic.net
> for detailed information.
> [stalls here forever]
>
> The message is sent in 3 packet and you see packet 1 and 3, 2 is
> lost and despite selective acks it is never seen.

that appears to be the case :( setting MSS to 1420 seems to work for
me (at home, on a janky tunneled setup, because you know... ipv6 is
'hard' for vz to do :( )

-chris