No offence, but I don't think you quite understand what I've been saying.
[I'm cc'ing this to the dev-list, because I've been told in the past that
this is the best forum to find support for people in my situation. I don't
think your email contained anything personal or private, and I'm not trying
to shame you or anything ... I simply need some answers, and the regular
OpenSRS support channels aren't able to provide it.]
> Sorry, Resellers don't get to talk to the developers. They have enough
> work to do :)
That's fine: I'm a developer too and I don't want to be bugged with support
issues all day. However, I think issues (issues that affect all of your
resellers, AFAICT) should be brought to their attention through *some*
channel. I don't need to speak to anyone personally, I just need to get the
message through. I get the sense that my emails don't get past the front
line of support personnel.
[Also please consider the fact that, as author of the PHP-interface to
OpenSRS, I'm speaking on behalf of not only myself, but all the resellers
who use this interface.]
> Please be aware that Resellers are completely responsible
> for any development. We can offer advice but not much else.
OpenSRS has it's scripts, and it has a published API. You do give
permission to resellers to either use your scripts, or to develop their own
scripts to talk to the API. So, why isn't someone at OpenSRS (be it
support staff, or someone from the development team) able to answer
questions about interfacing with OpenSRS through your API? Not everyone
likes Perl, remember. :)
You should be offering more than "advice". I don't think the current
situation is satisfactory, nor does it keeping with the "open" part of
OpenSRS.
> There is no need to register Live domains. Horizon behaves exactly like
> Live in these cases.
Except for registrar transfers ... and the fact that there are very few
name servers registered with Horizon, and ... ;)
This is a side point, though.
> Although Versign will allow you to register a domain without name servers,
> our default scripts will not. That's just the way we wrote it.
>
> I'm guessing that the error you are encountering has more to do with
> command syntax than anything else. The vanilla scripts are a good
> reference since they have this part straightened out.
Well, according to my tests, your system *does* allow registrations without
name servers. Not only that, but a registration *with* name servers seems
to
be registered *without* name servers, if those name servers are
non-existent.
As far as I can tell, your client scripts don't do any checking for the
validity of name servers, so I can't see how this is a command syntax issue.
In this situation, my opinion is that the API server should at least report
an error, rather than register anyway with no name server assignment.
I have since discovered that my problems with modifying name servers came
down to a typo on my part. So, in that regard, you are right in that part
of my problems were syntactical.
Still, I feel that resellers like myself, who choose not to use your Perl
scripts, should be afforded a level of support that entails more than
"you're on your own". Especially when your API is full of wrong
information, omissions, and PDF errors.
--
Colin Viebrock
Co-Founder, easyDNS Technologies Inc.
http://www.easyDNS.com/
