[151702] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Quad-A records in Network Solutions ?

daemon@ATHENA.MIT.EDU (Rodrick Brown)
Wed Mar 28 20:25:59 2012

In-Reply-To: <4F7362F1.7000705@gmail.com>
From: Rodrick Brown <rodrick.brown@gmail.com>
Date: Wed, 28 Mar 2012 20:25:21 -0400
To: "carlos@lacnic.net" <carlos@lacnic.net>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On Mar 28, 2012, at 3:13 PM, Carlos Martinez-Cagnazzo <carlosm3011@gmail.com=
> wrote:

> I'm not convinced. What you mention is real, but the code they need is
> little more than a regular expression that can be found on Google and a
> 20-line script for testing lames. And a couple of weeks of testing, and
> I think I'm exaggerating.
>=20
> If they don't want to offer support for it, they can just put up some
> disclaimer.
>=20
> regards,
>=20
> Carlos
>=20

I absolutely agree with Carlos here this has got to be a joke or likelihood o=
f NETSOL being extremely lazy on their part possibly lack of demand? There i=
s absolutely no valid reason an update like this shouldn't be trivial to imp=
lement unless their system was built by IBM contractors :-)

The core functionality of any IP/DNS management system is the flexibility an=
d robustness to quickly add and remove address records. No matter how bad th=
e system was designed or implemented not being able to support new record ty=
pes is a complete FAIL on all counts especially from a veteran registrar lik=
e NETSOL.

Like others have stated stick it where it hurts the most and use another ven=
dor.

>=20
> On 3/28/12 3:55 PM, David Conrad wrote:
>> On Mar 28, 2012, at 11:47 AM, Carlos Martinez-Cagnazzo wrote:
>>> I'm not a fan of conspiracy theories, but, c'mon. For a provisioning
>>> system, an AAAA record is just a fragging string, just like any other
>>> DNS record. How difficult to support can it be ?
>>=20
>> Of course it is more than a string. It requires touching code, (hopefully=
) testing that code, deploying it, training customer support staff to answer=
 questions, updating documentation, etc. Presumably Netsol did the cost/bene=
fit analysis and decided the potential increase in revenue generated by the v=
ast hordes of people demanding IPv6 (or the potential lost in revenue as the=
 vast hordes transfer away) didn't justify the expense. Simple business deci=
sion.
>>=20
>> Regards,
>> -drc
>>=20
>>=20
>=20


home help back first fref pref prev next nref lref last post