From a46173f1118119230780fc968433f57871844877 Mon Sep 17 00:00:00 2001 From: Shreyas Zare Date: Sun, 31 Jul 2022 15:37:12 +0530 Subject: [PATCH] minor update to apidocs --- APIDOCS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/APIDOCS.md b/APIDOCS.md index de27b38c..2684d0ac 100644 --- a/APIDOCS.md +++ b/APIDOCS.md @@ -3351,7 +3351,7 @@ WHERE: - `server`: The name server to query using the DNS client. - `domain`: The domain name to query. - `type`: The type of the query. -- `protocol` (optional): The DNS transport protocol to be used to query. Valid values are [`Udp`, `Tcp`, `Tls`, `Https`]. The default value of `Udp` is used when the parameter is missing. +- `protocol` (optional): The DNS transport protocol to be used to query. Valid values are [`Udp`, `Tcp`, `Tls`, `Https`, `HttpsJson`]. The default value of `Udp` is used when the parameter is missing. - `dnssec` (optional): Set to `true` to enable DNSSEC validation. - `import` (optional): This parameter when set to `true` indicates that the response of the DNS query should be imported in the an authoritative zone on this DNS server. Default value is `false` when this parameter is missing. If a zone does not exists, a primary zone for the `domain` name is created and the records from the response are set into the zone. Import can be done only for primary and forwarder type of zones. When `type` is set to AXFR, then the import feature will work as if a zone transfer was requested and the complete zone will be updated as per the zone transfer response. Note that any existing record type for the given `type` will be overwritten when syncing the records. It is recommended to use `recursive-resolver` or the actual name server address for the `server` parameter when importing records.