Response Samples

Changing status of a single name server

This request packet makes the DNS server act as a secondary for the zone specified by site ID 1.

<packet version="1.6.3.0">

<dns>

 <switch>

  <filter>

   <site-id>1</site-id>

  </filter>

  <zone_type>slave</zone_type>

 </switch>

</dns>

</packet>

The positive response from the server looks as follows:

<packet version="1.6.3.0">

<dns>

 <switch>

  <result>

   <status>ok</status>

   <site-id>1</site-id>

  </result>

 </switch>

</dns>

</packet>

A negative response from the server can look as follows:

<packet version="1.6.3.0">

<dns>

 <switch>

  <result>

   <status>error</status>

   <errcode>1015</errcode>

   <errtext>site does not exist</errtext>

   <site-id>1</site-id>

  </result>

 </switch>

</dns>

</packet>

Changing status of multiple name servers

This packet makes the DNS server act as a secondary for the zones specified by sites ID 1 and ID 2.

<packet version="1.6.3.0">

<dns>

 <switch>

  <filter>

   <site-id>1</site-id>

   <site-id>2</site-id>

  </filter>

  <zone_type>slave</zone_type>

 </switch>

</dns>

</packet>

A response packet from the server can look as follows:

<packet version="1.6.3.0">

<dns>

 <switch>

  <result>

   <status>ok</status>

   <site-id>1</site-id>

  </result>

  <result>

   <status>error</status>

   <errcode>1015</errcode>

   <errtext>site does not exist</errtext>

   <site-id>2</site-id>

  </result>

 </switch>

</dns>

</packet>

Please send us your feedback on this help page.