RRPproxy Homepage
RRPproxy Homepage


IPv6 name server addresses will be normalized in RRPproxy to match the preferred format defined in RFC-4291. IPv6 addresses can be stated in all valid formats, but will be normalized by our system. Excerpt from RFC-4291 regarding preferred form (https://tools.ietf.org/html/rfc4291): 2.2. Text Representation of Addresses There are three conventional forms for representing IPv6 addresses as text strings: 1. The preferred form is x:x:x:x:x:x:x:x, where the 'x's are one to four hexadecimal digits of the eight 16-bit pieces of the address. Examples: ABCD:EF01:2345:6789:ABCD:EF01:2345:6789 2001:DB8:0:0:8:800:200C:417A

Possible Gateways

The command StatusNameserver is available via the following gateways:

Required Parameters

The following parameters are standard parameters for this command.


COMMAND = StatusNameserver


code = (INT)
description = (TEXT)
property[REGISTRAR][0] = (TEXT)
property[NAMESERVER][0] = (TEXT)
property[IPADDRESS][n] = (IPADDRESS)
property[CREATED_DATE][0] = (DATE)
property[CREATED_BY][0] = (TEXT)
property[UPDATED_DATE][0] = (DATE)
property[UPDATED_BY][0] = (TEXT)
property[STATUS][n] = (TEXT)


NAMESERVER Nameserver to fetch the details for
NAMESERVER Hostname of the nameserver
IPADDRESS IP - address(es) of the nameserver
CREATED_DATE Date, when the nameserver was created
CREATED_BY Account the nameserver was created in
UPDATED_DATE Date, when the nameserver was last updated
UPDATED_BY Account, who did the last update for the nameserver

Wedomains :)