Hello all,
I'm woking on reimplementing the OpenSRS client for our company. (We
have different end-user requirements that the CGIs don't really meet.)
I've been having a problem trying to get the "Modify Nameservers"
functionality built.
The client is written in Perl using the OpenSRS module (2.0.1
currently). The problem I'm having is when I
Client->send_cmd("get_nameservers") to the OpenSRS server, for some
domains it returns information regarding the nameservers, other domains
it returns nothing except a success response, even though those domains
definitely have nameserver records in the OpenSRS database. (Note that
the server request returns *successfully*, not with an error!)
The domains seem to be pretty consistent as to which return values and
which do not, at least as far as the same ones behaving the same way,
not neccesarily that they make any sense which ones work and which do
not. The manage.cgi also kicks me out to the login page when I try to
retrieve nameserver information for some of the domains I cannot
retrieve. Both of those symptoms make me suspect that the profile those
domains have been registered under are not allowed access to nameserver
records, but according to the guys I work with, that should not be the
case as ALL our domains were moved to the same top-level profile as one
of the first steps in setting up our account with OpenSRS.
Further, if we register a new domain, creating a new profile for it and
then immediately attempt to view nameserver records using that profile,
we will also usually get returned an empty "success" response.
Coincidentally (or not) I have been unable to retrieve nameserver for
*any* domain through the OpenSRS test server (horizon) with my client
code.
I've contacted our contact at OpenSRS and he recommended that I post
this to the dev-list. I'm kind of new to the whole OpenSRS thing (I've
been working on it part-time for about two weeks or so) so it's entirely
possible that this might just be a big misunderstanding in the way
things actually work. (But considering the situation two paragraphs
above, I'm doubtful of that.)
This is becoming a real stick in our eye, holding up deployment of the
service to our clients, so any help anyone can give would be greatly
appreciated.
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
With Microsoft products, failure is not Derek Glidden
an option - it's a standard component. http://3dlinux.org/
Choose your life. Choose your http://www.tbcpc.org/
future. Choose Linux. http://www.illusionary.com/
