5.4.3. Info nsset¶
A nsset info command is used to view details of an nsset.
The nsset info command is an info
element in the nsset
namespace
(http://www.nic.cz/xml/epp/nsset-1.2
).
The command must be contained in the <info>
command type.
5.4.3.1. Command element structure¶
The <nsset:info>
element must declare the nsset
namespace and schema and it must contain the following child element:
<nsset:id>
(1) – an nsset handle as fredcom:objIDType.<nsset:authInfo>
(0..1) – the authorization information (AuthInfo) as fredcom:authInfoType.
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
<command>
<info>
<nsset:info xmlns:nsset="http://www.nic.cz/xml/epp/nsset-1.2"
xsi:schemaLocation="http://www.nic.cz/xml/epp/nsset-1.2 nsset-1.2.4.xsd">
<nsset:id>NID-MYNSSET</nsset:id>
<nsset:authInfo>MyPassword</nsset:authInfo>
</nsset:info>
</info>
<clTRID>kttq005#17-07-31at12:21:02</clTRID>
</command>
</epp>
> info_nsset NID-MYNSSET MyPassword
5.4.3.2. Response element structure¶
The response from the FRED EPP server contains the result, response data, and transaction identification.
See also Success or failure of a command.
The response data element (<resData>
) contains a single child element
<nsset:infData>
which declares the nsset
namespace and schema
and it contains the following child elements:
<nsset:id>
(1) – the nsset handle as fredcom:objIDType,<nsset:roid>
(1) – the nsset repository identifier as eppcom:roidType,<nsset:status>
(1..n) – the nsset object state(s):@s
(R) – the state name as one of values:ok
linked
serverDeleteProhibited
serverTransferProhibited
serverUpdateProhibited
deleteCandidate
@lang
– the language of the state description as a xs:language (default:en
),element content: the state description as a xs:normalizedString,
<nsset:clID>
(1) – the designated registrar’s handle as eppcom:clIDType,<nsset:crID>
(0..1) – the handle of the registrar who created this nsset as eppcom:clIDType,<nsset:crDate>
(0..1) – the timestamp of creation as xs:dateTime,<nsset:upID>
(0..1) – the handle of the registrar who was the last to update this nsset as eppcom:clIDType,<nsset:upDate>
(0..1) – the timestamp of the last update as xs:dateTime,<nsset:trDate>
(0..1) – the timestamp of the last transfer as xs:dateTime,<nsset:authInfo>
(0..1) – the authorization information (AuthInfo) as fredcom:authInfoType,<nsset:ns>
(0..10) – a nameserver given by:<nsset:name>
(1) – a nameserver hostname as eppcom:labelType,<nsset:addr>
(0..n) – a namesever’s IP address as nsset:addrStringType,
<nsset:tech>
(1..n) – a technical contact handle as fredcom:objIDType,<nsset:reportlevel>
(1) – the report level of technical checks as nsset:reportlevelType.
<?xml version="1.0" encoding="UTF-8"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
<response>
<result code="1000">
<msg>Command completed successfully</msg>
</result>
<resData>
<nsset:infData xmlns:nsset="http://www.nic.cz/xml/epp/nsset-1.2"
xsi:schemaLocation="http://www.nic.cz/xml/epp/nsset-1.2 nsset-1.2.4.xsd">
<nsset:id>NID-MYNSSET</nsset:id>
<nsset:roid>N0009907595-CZ</nsset:roid>
<nsset:status s="linked">Has relation to other records in the registry</nsset:status>
<nsset:clID>REG-MYREG</nsset:clID>
<nsset:crID>REG-MYREG</nsset:crID>
<nsset:crDate>2017-07-11T13:28:42+02:00</nsset:crDate>
<nsset:upID>REG-MYREG</nsset:upID>
<nsset:upDate>2017-07-27T16:54:53+02:00</nsset:upDate>
<nsset:ns>
<nsset:name>ns1.mydomain.cz</nsset:name>
<nsset:addr>111.222.111.222</nsset:addr>
</nsset:ns>
<nsset:ns>
<nsset:name>ns.otherdomain.cz</nsset:name>
</nsset:ns>
<nsset:tech>CID-TECH2</nsset:tech>
<nsset:reportlevel>4</nsset:reportlevel>
</nsset:infData>
</resData>
<trID>
<clTRID>kttq005#17-07-31at12:21:02</clTRID>
<svTRID>ReqID-0000140998</svTRID>
</trID>
</response>
</epp>