I've got one and a half answers for you *grin* You can use default.opensrs.org and default2.opensrs.org, as well as cns1.idirect.com and cns2.idirect.com; any nameserver that you create will be useable as well.
This question is best sent to dev-list; I'll take a crack here. You need only send in the IP part of the hash if you're creating/modifying the nameserver hosts. Otherwise, just the hostname will suffice. You also do not need to send blank references (for nameserver 3-6 as you've done here), and the sort order isn't really important since the root registry round robins nameservers, so the order is moot (except for the aesthetic value of how the nameservers showup in whois). Charles Daminato OpenSRS Product Manager Tucows Inc. - [EMAIL PROTECTED] > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Tim Woodcock > Sent: February 4, 2002 6:43 PM > To: [EMAIL PROTECTED] > Subject: DNS servers > > > > I have two questions. > > First, I have been told that there are DNS servers that work in the > horizon system other than ns{1,2}.domaindirect.com. > > Does anyone have a list? > > > Second: > > We are having a problem setting DNS servers during the registration > process with sw_register. We are using the perl client, and we are > sending the following format for the nameserver_list component: > > 'nameserver_list' => [ > { > 'name' => 'ns1.domain-dns.com', > 'sortorder' => 1, > 'ipaddress' => '' > }, > { > 'name' => 'ns2.domain-dns.com', > 'sortorder' => 2, > 'ipaddress' => '' > }, > {}, > {}, > {}, > {} > ], > > The DNS servers above have been changed from what was sent, but both > servers that were sent answer queries. > > Is the ipaddress argument legitimate? > It is not in the documentation. I am not sure where we picked it > up from. > There has to be some way to specify IP addresses so that you can set up > DNS servers within the domain you are registering. > > I have not yet tried sending the requests without the blank ipaddress > field. > > This seems to be a recent problem. It is possible that it appeared when > we converted from register to sw_register, but it could be more recent. > >
