I disagree.
Noted
In general our business model is based around not exposing our clients to
any
technical complexity we can avoid.
As such I've yet to see a domain name registration and management system
that
would be suitable for the majority of our clients. They don't know about
DNS,
and whilst it works they don't care either. Indeed I would say this model
is
the correct model for retail Internet services.
So the first course of action is for our clients to contact us.
So, why did you disagree? This is EXACTLY what I said.
In cases where they have contacted TUCOWS, TUCOWS usually refer the client
to
us, in cases where they haven't TUCOWS have made some horrendous mistakes.
As I said in my initial post, the client contacted the reseller. The
reseller told them to contact Tucows. Tucows sent them back to the reseller,
and the reseller pointed them to adminchange.com. I maintain this should NOT
(nor should it EVER) be the first course of action for a client to get the
CORRECT contact information (the contact information which has NEVER changed
and which the reseller was provided with at the outset) sent to the
registry.
We have several domains currently being disputed between husband and wife,
or
between former business partners, where TUCOWS attempting to intervene and
doing "the obvious thing" is unlikely to be helpful or useful.
I am not talking about a dispute between business partners or estranged
couples. I am talking about a reseller who is refusing to allow an end-user
access to a domain name which the end-user has paid for.
If you have evidence (as you claim) of willful obstruction, just send it
to
TUCOWS, but don't assume your business model is the only one.
What did I say about my business model?
I have submitted said info to Tucows and they have pointed us to
adminchange.com, which, as I said, is not (or, at least, should not be) the
best first course of action.
Brian
_______________________________________________
domains-gen mailing list
[email protected]
http://discuss.tucows.com/mailman/listinfo/domains-gen
