Another reason to not use them.
Seriusly, if they cannot expend some thousands of dollars (because
it shouldn't be more than that) in "touching code, (hopefully) testing that
code, deploying it, training customer support staff to answer questions,
updating documentation, etc." I cannot take them as a serious provider for
Not having ipv6 and your website availability tied to some overloaded cgn
at an ISP you have no relationship with .... or your abuse policy just
blocked what you thought was a /24 ... turns out to be verizon nat44 space
for nyc ... and now x million customers can't click "buy now" ....
>> 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.
>> If they don't want to offer support for it, they can just put up some
>>>> 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 ?
>>> 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/benefit analysis and decided the potential increase in revenue
generated by the vast hordes of people demanding IPv6 (or the potential
lost in revenue as the vast hordes transfer away) didn't justify the
expense. Simple business decision.
> That's assuming their system is sanely or logically designed. It could
be a total disaster of code, which makes adding such a feature a major pain.