CentOS 6.9, jwis saída incompleta

Question

A partir de alguns dias, notei uma saída whois estranha sob o CentOS 6.9 com domínios .com:

whois google.com
[Interrogando whois.verisign-grs.com]
[whois.verisign-grs.com]
   Domain Name: GOOGLE.COM
   Registry Domain ID: 2138514_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.markmonitor.com
   Registrar URL: http://www.markmonitor.com
   Updated Date: 2011-07-20T16:55:31Z
   Creation Date: 1997-09-15T04:00:00Z
   Registry Expiry Date: 2020-09-14T04:00:00Z
   Registrar: MarkMonitor Inc.
   Registrar IANA ID: 292
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: [phone]
   Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
   Domain Status: serverDeleteProhibited https://icann.org/epp#serverDeleteProhibited
   Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
   Domain Status: serverUpdateProhibited https://icann.org/epp#serverUpdateProhibited
   Name Server: NS1.GOOGLE.COM
   Name Server: NS2.GOOGLE.COM
   Name Server: NS3.GOOGLE.COM
   Name Server: NS4.GOOGLE.COM
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2017-07-31T15:24:36Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar.  Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability.  VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

A partir do CentOS 7, posso ver a saída whois clássica e completa:

whois google.com
[Interrogando whois.verisign-grs.com]
[Redirezione verso whois.markmonitor.com]
[Interrogando whois.markmonitor.com]
[whois.markmonitor.com]
Domain Name: google.com
Registry Domain ID: 2138514_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2015-06-12T10:38:52-0700
Creation Date: 1997-09-15T00:00:00-0700
Registrar Registration Expiration Date: 2020-09-13T21:00:00-0700
Registrar: MarkMonitor, Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: [phone]
Domain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)
Domain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)
Domain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)
Domain Status: serverUpdateProhibited (https://www.icann.org/epp#serverUpdateProhibited)
Domain Status: serverTransferProhibited (https://www.icann.org/epp#serverTransferProhibited)
Domain Status: serverDeleteProhibited (https://www.icann.org/epp#serverDeleteProhibited)
Registry Registrant ID: 
Registrant Name: Dns Admin
Registrant Organization: Google Inc.
Registrant Street: Please contact [email protected], 1600 Amphitheatre Parkway
Registrant City: Mountain View
Registrant State/Province: CA
Registrant Postal Code: 94043
Registrant Country: US
Registrant Phone: [phone]
Registrant Phone Ext: 
Registrant Fax: [phone]
Registrant Fax Ext: 
Registrant Email: [email protected]
Registry Admin ID: 
Admin Name: DNS Admin
Admin Organization: Google Inc.
Admin Street: 1600 Amphitheatre Parkway
Admin City: Mountain View
Admin State/Province: CA
Admin Postal Code: 94043
Admin Country: US
Admin Phone: [phone]
Admin Phone Ext: 
Admin Fax: [phone]
Admin Fax Ext: 
Admin Email: [email protected]
Registry Tech ID: 
Tech Name: DNS Admin
Tech Organization: Google Inc.
Tech Street: 2400 E. Bayshore Pkwy
Tech City: Mountain View
Tech State/Province: CA
Tech Postal Code: 94043
Tech Country: US
Tech Phone: [phone]
Tech Phone Ext: 
Tech Fax: [phone]
Tech Fax Ext: 
Tech Email: [email protected]
Name Server: ns1.google.com
Name Server: ns4.google.com
Name Server: ns2.google.com
Name Server: ns3.google.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2017-07-31T07:15:42-0700 <<<

The Data in MarkMonitor.com's WHOIS database is provided by MarkMonitor.com for
information purposes, and to assist persons in obtaining information about or
related to a domain name registration record.  MarkMonitor.com does not guarantee
its accuracy.  By submitting a WHOIS query, you agree that you will use this Data
only for lawful purposes and that, under no circumstances will you use this Data to:
 (1) allow, enable, or otherwise support the transmission of mass unsolicited,
     commercial advertising or solicitations via e-mail (spam); or
 (2) enable high volume, automated, electronic processes that apply to
     MarkMonitor.com (or its systems).
MarkMonitor.com reserves the right to modify these terms at any time.
By submitting this query, you agree to abide by this policy.

MarkMonitor is the Global Leader in Online Brand Protection.

MarkMonitor Domain Management(TM)
MarkMonitor Brand Protection(TM)
MarkMonitor AntiPiracy(TM)
MarkMonitor AntiFraud(TM)
Professional and Managed Services

Visit MarkMonitor at http://www.markmonitor.com
Contact us at +1.8007459229
In Europe, at +44.02032062220

For more information on Whois status codes, please visit
 https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en
--

A primeira (e única) coisa útil que noto é que, no CentOS 6.9, o whois não faz o redirecionamento para whois.markmonitor.com:

[Interrogando whois.verisign-grs.com]
[Redirezione verso whois.markmonitor.com]
[Interrogando whois.markmonitor.com]

Alguém sabe alguma coisa sobre isso? Isso aconteceu pela primeira vez na semana passada ...

    

Answer 1

Acho que você já descreveu o problema e sua resposta: o antigo cliente whois não faz um redirecionamento automático para o registrador whois. Compare as versões dos dois clientes whois.

O fato é que atualmente (ele será alterado nos meses seguintes), os nomes de domínio .COM / NET ainda são tratados em um registro "thin". Isso significa que o registro (VeriSign) gera um whois com apenas informações básicas e, por exemplo, sem dados de contato. No entanto, nesta saída, você pode ver o registrador responsável e seu próprio whois, portanto, um cliente "inteligente" detectará isso e refazerá a consulta ao registrador whois para coletar dados adicionais.

O protocolo whois foi subdesenhado e toda essa coisa de "redirecionamento" não é especificada em lugar nenhum. É apenas que alguns clientes ficaram mais espertos na esperança de serem capazes de lidar com todos os casos de whois "divididos". Então, um cliente pode fazê-lo corretamente e outro não. Mas, em todos os casos, você sempre pode especificar explicitamente o servidor whois que deseja consultar, portanto, caso o redirecionamento não aconteça, você poderá refazer a consulta para o servidor whois do registrador. Ou apenas atualize seu cliente.

    

Answer 2

OBSERVAÇÃO: Estou adicionando uma solução alternativa para jwhois no CentOS 6. Vou definir a resposta de Patrick como solução, porque me ajudou muito a entrar nos trilhos corretos para encontrá-la.

Na verdade, o CentOS 6 usa apenas jwhois 4.0-19, o CentOs 7 usa jwhois 4.0.48 que redirecionam corretamente. Eu não consegui encontrar uma atualização para o 4.0.48 para o CentOS 6, então eu resolvi editar o /etc/jwhois.conf para forçar o jwhois a usar o whois.markmonitor.com para procuras .com e .net.

então eu mudei:

"\.com$" {
        whois-server = "whois.verisign-grs.com";
        query-format = "domain $*";
}

em

"\.com$" {
        whois-server = "whois.markmonitor.com";
}

e

"\.net$" {
        whois-server = "whois.verisign-grs.com";
        query-format = "domain $*";
}

em

"\.net$" {
        whois-server = "whois.markmonitor.com";
}

E agora as consultas whois funcionam bem com .com e .net (esperamos que espere por uma atualização ...)