DNS BIND Record

GET POST/api/2.0/fo/auth/bind

List, create, update DNS BIND authentication records for compliance scans (using PC). Compliance scans are supported (using PC).

Input ParametersInput Parameters

Parameter	Required/Optional	Data Type	Description
action	Required	String	Specify to list, create, update, delete, authentication records.
ids	Required	Integer	Specify a single or comma separated valid DNS BIND type authentication record ID(s).
title	Required	Alphanumeric	Specify the title for the authentication record.
ips	Required	Integer	Specify the IP address(es) the server will log into using the record’s credentials. Multiple entries are comma separated.
unix_bin_path	Required	Path	Specify absolute path of the DNS BIND Base64 encoded binary file location. Base64 encoded binary file path. Example- "/usr/sbin/named".
unix_conf_path	Required	Path	Specify absolute path of the DNS BIND Base64 encoded configuration file path. Example- "/etc/named.conf".
base_directory	Optional	Path	Specify Base64 encoded base directory. In BIND configuration file, if an include file is relative path, it is relative to this base_dir. Optional field, if not present, it will be derived from conf_path. Example- If conf_path is /etc/named.conf and if base_dir is not specified, then base_dir is set to "/etc". It must be absolute path if specified.
chroot_directory	Optional	Path	Specify Base64 encoded chroot directory. Optional field, only needed if BIND runs in a self contained environment. If present, must be absolute path and it will be prefixed to all other 3 paths. Example- If chroot_dir is "/var/bind" and if bin_path is "/usr/sbin/named", then the final bin_path will be "/var/bind/usr/sbin/named".

Sample - List DNS BIND RecordsSample - List DNS BIND Records

API request

curl" -d "action=list" "<qualys_base_url>/api/2.0/fo/auth/bind/"

XML output

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE AUTH_CISCO_APIC_LIST_OUTPUT SYSTEM
"<qualys_base_url>/api/2.0/fo/auth/cisco_apic/auth_cisco_apic_list_
output.dtd">
<AUTH_CISCO_APIC_LIST_OUTPUT>
 <RESPONSE>
 <AUTH_CISCO_APIC_LIST>
<AUTH_CISCO_APIC>
<ID>dummy text</ID>
<TITLE><![CDATA[user 1]]></TITLE>
<USERNAME><![CDATA[user 1]]></USERNAME>
<PORT>444</PORT>
<WINDOWS_DOMAIN><![CDATA[aaaa]]></WINDOWS_DOMAIN>
 <SSL_VERIFY><![CDATA[1]]></SSL_VERIFY>
 <IP_SET>
<IP>3.3.3.3</IP>
 </IP_SET>
 <REQUIRE_CERT><![CDATA[1]]></REQUIRE_CERT>
 <DOMAIN><![CDATA[aaaa]]></DOMAIN>
 <PORT><![CDATA[444]]></PORT>
 <SSL_VERIFY_WITH_HOST><![CDATA[1]]></SSL_VERIFY_WITH_HOST>
 <LOGIN_TYPE><![CDATA[basic]]></LOGIN_TYPE>
 <CREATED>
<BY>user_1</BY>
 </CREATED>
 </AUTH_CISCO_APIC>
 </AUTH_CISCO_APIC_LIST>
 </RESPONSE>
</AUTH_CISCO_APIC_LIST_OUTPUT>

Sample - Create DNS BIND RecordsSample - Create DNS BIND Records

API request

curl" -d"action=create&ips=40.40.40.6&title=user_1bind2c&unix_bin_path=/etc&unix_conf_path=/etc/bind" "<qualys_base_url>:48443/api/2.0/fo/auth/bind/"

XML output

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE BATCH_RETURN SYSTEM
"<qualys_base_url>/api/2.0/batch_return.dtd">
<BATCH_RETURN>
 <BATCH_LIST>
<BATCH>
<TEXT>Successfully Created</TEXT>
<ID_SET>
 <ID>dummy text</ID>
</ID_SET>
</BATCH>
 </BATCH_LIST>
 </RESPONSE>
</BATCH_RETURN>

Sample - Update DNS BIND RecordsSample - Update DNS BIND Records

API request

curl" -d "action=update&ids=7882778&title=testbind""<qualys_base_url>:48443/api/2.0/fo/auth/bind/"

XML output

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE BATCH_RETURN SYSTEM
"<qualys_base_url>/api/2.0/batch_return.dtd">
<BATCH_RETURN>
 <BATCH_LIST>
<BATCH>
<TEXT>Successfully Updated</TEXT>
<ID_SET>
 <ID>dummy text</ID>
</ID_SET>
</BATCH>
 </BATCH_LIST>
 </RESPONSE>
</BATCH_RETURN>

DTDs for Authentication Type “cisco”

Qualys API Server URL/api/2.0/batch_return.dtd

Qualys API Server URL/api/2.0/fo/auth/auth_bind_list_output.dtd