[30338] in North American Network Operators' Group
RE: whois databases and null fields
daemon@ATHENA.MIT.EDU (Carter, Gregory)
Thu Jul 27 00:07:57 2000
Message-ID: <C169E193B2ECD3118923006097713166046295@NACAMX01B>
From: "Carter, Gregory" <omni@dynmc.net>
To: nanog@merit.edu
Date: Wed, 26 Jul 2000 21:18:11 -0700
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Errors-To: owner-nanog-outgoing@merit.edu
-----BEGIN PGP SIGNED MESSAGE-----
Just thought you all might be interested to know that these null fields that
are showing up may seem innocent but they are affecting some other registrars.
I had a customer use my company to transfer their domain names from NSI, out of
the three domain names only one of them successfully sent him the admin contact
email address the OpenSRS confirmation. Unfortunately I had to wait another 3
to 4 days before the requests expired so that they could be sent again.
Wanted to give you all a heads up for those of you that use the OpenSRS system.
I haven't heard any reports of any other registrars having this problem but
still worth keeping a close eye on.
Greg
+(gcarter@infoDNS.com)-------------------------------------------------+
| infoDNS http://www.infodns.com/ |
| Senior Network Administrator bits/keyID 1024/7DF9C285 |
| Register your domain name today for only $25/yr. |
+--------[ DC 50 57 59 C3 76 46 E8 EB 75 A8 94 FE 96 9E D3 ]----------+
- -----Original Message-----
From: Nathan Lane [mailto:nathan@terminus.com]
Sent: Wednesday, July 26, 2000 7:24 PM
To: nanog@merit.edu
Subject: Re: whois databases and null fields
A few nights ago it was worse. Instead of nulls, the registrar fields
were incorrect indicating a completely different server and registrar
(many of which did not exist or were non-functional.) The registrant
and nameservers appeared correctly.
Hopefully they will become driven to operational excellence and I've
seen a few steps that way, but money, not process and service, seems to
be driving them for the short term.
- -Nathan Lane
Network Engineer
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.3
iQCVAwUBOX+2YW2piax9+cKFAQHZewQAnjcx9XWb4JvnPWtX7Y+ht8mzw5LERD4h
e165qqSPaMvsmlTgPREozx1komeSZwyvRuR33qfkxxuJFhCehWmOpaBCVPIDxNcX
KBDPml34XFt8wHNoHGyysGXBwsz1sjeuLGxqSTgauki5OaHpAT3DTd9LhX9wN67/
sWdLURDuViE=
=AgDS
-----END PGP SIGNATURE-----
