Modify DNS


CGI-Server Connection Path

Live: http://www.onlinenic.com/cgi-bin/english/b_domain_mod_dns.cgi


Parameters submitted by reseller

user_id  Reseller's user ID at OnlineNIC.
order_id Your server must generate a unique order id.
o_time Order's generation time,Format:YYYY-MM-DD HH:MM:SS. For example: 2000-02-20 12£º03£º33
url The CGI address reseller provides to handle OnlineNIC's feedback messages. After OnlineNIC handles the request, the feedback message is sent to this CGI.
checksum Md5 checksum between reseller and OnlineNIC. (see note below)
domain Domain to me modified.
dns_old_1 Present primary DNS
dns_old_2 Present secondary DNS
dns_new_1 New primary DNS
dns_new_2 New secondary DNS

Note: The checksum is generated like this:

checksum = md5(user_id+order_id+o_time+url+md5(password)+domain)

The password is your OnlineNIC reseller password. The other parameters are identical to the values submitted by your server.


It is suggested that reseller submits forms in the following format:

<form action="http://www.onlinenic.com/cgi-bin/english/b_domain_mod_dns.cgi" method=POST name=a_reg>
<input type="hidden" name="user_id" value="10575">
<input type="hidden" name="order_id" value="1">
<input type="hidden" name="o_time" value="2000-06-18 20:00:00">
<input type="hidden" name="url" value="http://yourserver.com/yourscript.php">
<input type="hidden" name="checksum" value="419021bc54f522ecfe8903a7895735f5">
<input type="hidden" name="domain" value="3wabcdefg.net">
<input type="hidden" name="dns_old_1" value="ns3.onlinenic.com">
<input type="hidden" name="dns_old_2" value="ns4.onlinenic.com">
<input type="hidden" name="dns_new_1" value="ns3.nazha.com">
<input type="hidden" name="dns_new_2" value="ns4.nazha.com">
<input type="submit" value="Submit">
</form>


OnlineNIC server return values

user_id Reseller's user ID at OnlineNIC
order_id Reseller's order ID.
o_time Order's generation time (the time when reseller submitted order)
success Result of call to OnlineNIC server, starting with result code, and ending with result message. A "0" indicates success. A non-zero code indicates failure. Most failure repsonses will include a text message explaining the error.
checksum MD5 checksum. Reseller can use this checksum to confirm the validity of the response.

The checksum is generated like this:

checksum = md5(user_id+order_id+o_time+success+md5(password))

The password is your OnlineNIC reseller password. The other parameters are identical to those submitted by your server.