...maybe it would be more constructive to simply say "Oh,
well, this doesn't meet my needs. I guess I'll find another service
offering (or roll my own) to do what I need it to do.
I don't believe so ..
If OpenSRS don't get this sort of feedback then they won't know what
areas and customer requirements are not met or where customers think
they have got it wrong - your suggested approach is any suppliers worst
enemy.
I have concerns about some of the limitations of the DNS service but
more so the actual decision making process behind these limitations. If
the decision making process is flawed for one service it has the
potential to be flawed for others and this could ultimately impact us
all.
I do not believe that the quality and completeness of the services
starting from when certificate services were introduced are what they
should or could be. Often promised improvements do not appear and major
enhancements do not appear - the prime example being the client code and
its strategic direction (The SourceForge client then not the SourceForge
but all the oft requested features and enhancements of the "alternative"
client are still not implemented in the official client.
As raised earlier on in this thread by someone else, when the new
services from OpenSRS arrive they are incomplete solutions offerings
without the extra bells and whistles required to differentiate the
offering.
As an existing customer of OpenSRS I want to see them do well as that
can only be good for me in the long run and it is therefore in my best
interests to shout when I think they have got it wrong.
I for one am not going to look elsewhere for one element of the service
if I can get the right solution at the right price from a single
supplier and so the consequence of these issues will be lost customers
for all services rather than not winning customers for one service. If
necessary I will look elsewhere but I don't want to have to do that and
unless I voice my concerns OpenSRS don't have an opportunity to address
them.
Regards
Rob
-----Original Message-----
From: owner-discuss-list@opensrs.org
[mailto:owner-discuss-list@opensrs.org] On Behalf Of WebWiz
Sent: 03 February 2004 18:03
To: discuss-list@opensrs.org
Subject: Re: Managed DNS Service concerns
Rob,
Isn't this, then, just an indication that the service that TUCOWS is
offering doesn't meet *YOUR* needs? It sounds like you have some very
specific requirements that don't happen to be met by the vanilla
offering that TUCOWS has available. Rather than lambasting TUCOWS for
their offering, maybe it would be more constructive to simply say "Oh,
well, this doesn't meet my needs. I guess I'll find another service
offering (or roll my own) to do what I need it to do."
Remember that TUCOWS put together a service that's designed to meet the
generic needs of a large group of people. They made design decisions
that, apparently, make the service of less value to you personally. As
described, it would work great for me, but I already run my own DNS
servers, so I don't feel compelled to pursue it.
What I'm trying to say is this: If it won't work for you, then don't
use it and quit fussing about it. Make your enhancement requests and
move on. Re-evaluate it later when TUCOWS has had an opportunity to
possibly implement some of your suggestions.
My $0.02 (but then again, maybe I'm just grumpy today).
Regards,
Eric Longman
Atl-Connect Internet Services
+-------------------------------------------------------+
| Atl-Connect Internet Services http://www.atlcon.net |
| 3600 Dallas Hwy Ste 230-288 770 590-0888 |
| Marietta, GA 30064-1685 support@atlcon.net |
+-------------------------------------------------------+
Rob wrote:
> I do not agree - the only reason that the capability for editing the
> TTLs is not present is due to a conscious decision by OpenSRS either
to
> not implement this capability or that it should not be edited - I
think
> it is fairly clear from the comments a number of people have made on
> this list that this was a bad decision and does indicate a lack of
> understanding on how DNS is being used in the real world.
>
> If the ability to add editing the domain contact can be implemented so
> quickly why cannot editing the other TTL values be implemented at the
> same time ?
> I cannot see why this should require any significant technical effort
> from OpenSRS to achieve.
>
> Your previous comments regarding email and the fact that you seem to
> think that TTL issues are in someway related to wanting a Dynamic DNS
> service demonstrates a complete and fundamental misunderstanding of
what
> is being asked for and of DNS itself.
>
> Regards
> Rob
>
<snip>
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:37:54 EDT