The disable operation is used to disable the local DNS support for the current zone. With the operation, you can also disable the local DNS support for the DNS zone template. All the sites or site alias zones, which were added according to the template with the disabled status, will not be supported by local DNS. You can enable the local DNS support for multiple zones in a single packet.
To learn how to retrieve the status information for the local DNS server, refer to the Managing SOA Records and Zone Parameters section.
A request XML packet switching off the local DNS support includes the disable operation node:
<packet version="1.4.2.0">
<dns>
<disable>
...
</disable>
</dns>
</packet>
The graphical representation of the disable node is as follows:
dns_input.xsd
).You can disable the local DNS support for multiple zones. Add as many disable operations as the number of different filtering rules.
<dns>
<disable>
...
</disable>
...
<disable>
...
</disable>
</dns>
The disable node of the output XML packet is structured as follows:
dns_output.xsd
).
This packet disables the local DNS for the zones specified by site ID 8 and ID 9.
<packet version="1.6.3.0">
<dns>
<disable>
<filter>
<site-id>8</site-id>
<site-id>9</site-id>
</filter>
</disable>
</dns>
</packet>
Response:
<packet version="1.6.3.0">
<dns>
<disable>
<result>
<status>ok</status>
<site-id>8</site-id>
</result>
<result>
<status>ok</status>
<site-id>9</site-id>
</result>
</disable>
</dns>
</packet>
This packet disables the local DNS for the DNS zone template .
<packet version="1.4.2.0">
<dns>
<disable/>
</dns>
</packet>
Response:
<?xml version="1.0" encoding="UTF-8"?>
<packet version="1.4.2.0">
<dns>
<disable>
<result>
<status>ok</status>
</result>
</disable>
</dns>
</packet>