Frank,

> > B) There seems to be a bug in the test system in that new registrations
are
> > not including nameserver information.  i.e., I register a name, it
completes
> > succesfully, yet there are no NS records for the domain.  Look at the
> > registration for FOOBART32.COM on the test (horizon) system.
>
> You're allowed to register domains without nameservice.   What i'm seeing
is
> that you did not send DNS information to us.  You realize the test server
only
> has a few nameservers, and you need to use ns1.domaindirect.com and ns2
for your
> test registrations, right?

I didn't realize that about the nameservers, but I did send DNS info with
the original registration (ns1.easydns.com and ns2.easydns.com, which exist
on the test system, AFAICT).


> > C) Similar to B) above, on the *live* system, if you supply bogus
nameserver
> > information (i.e. nameserver names that don't exist), the registration
will
> > complete succesfully, but no NS records are created.  Look at the
> > registration for TORONTOTHEATREALLIANCE.COM on the live system.

> Looking at the order on the live system, it seems you submitted it with no
> nameservers.  Thats what I see anyway.  I dont see normal nameserver
validation
> errors in the notes field of the domain.  Of course you can now go in and
manage
> the domain to add them.

I did submit it with nameserver information: dns1.foo-bart.com and
dns2.foo-bart.com, which purposefully don't exist.  This was to confirm with
Charles (who I've been speaking to previously) that this is a bug on both
the live and test systems.  I'm cc'ing him on this, so you can check with
him if you like.

It seems that bogus NS records are ignored.  I would expect that they should
generate a warning instead.


> > D) Can you tell me why this command failed?  This is for the domain
> > "JOE-TEST.ORG" on the test (horizon) system:
<snip>

Here is some further information on this, which I can't understand why it's
failing.

First a get_domain command to check the current nameservers:

    ...
            [nameserver_list] => Array
                (
                    [0] => Array
                        (
                            [ipaddress] => 205.210.42.21
                            [sortorder] => 1
                            [encoding_type] =>
                            [name] => ns1.easydns.com
                        )

                )
    ...

Then, I send a modify_domain command:

    [action] => modify
    [object] => domain
    [cookie] => 550269460:207224
    [attributes] => Array
        (
            [data] => nameserver_list
            [nameserver_list] => Array
                (
                    [action] => update
                    [name] => ns1.domaindirect.com
                    [sort_order] => 1
                )
        )

Result of modify_domain:

    [is_success] => 0
    [protocol] => XCP
    [_OPS_msg_type] => standard
    [object] => MODIFY
    [_OPS_msg_id] => 50.9894376751419
    [response_text] => Fatal Server Error Occured
    [response_code] => 400
    [action] => REPLY
    [_OPS_version] => 0.9


I don't think I'm doing anything wrong ...


> > E) Not that I want to swamp anyone with questions, but is there an email
> > address of one of the developers to whom I can send these type of
> > API-related questions directly (like D above)?  I'm sure it would make
> > things easier all around ... :)
>
>
> The best venue for this would be the [EMAIL PROTECTED]  You can search
the
> archives and signup here :
> http://www.opensrs.org/archives/mailing.index.shtml
>
> Hope this helps.

Somewhat. :) I'm on that list, and rarely do I get responses.  I'll cc this
to the list as well.

- Colin

Reply via email to