vania-janet/multiturn-rag-retrieval-data huggingface dataset:
<-- <section "id="section-list-cis-service-plans-options" "> --> Command options --refresh: Force refresh from catalog.--output: Specify output format, only JSON is supported.<-- </section "id="section-list-cis-service-plans-options" "> --><-- <section "id="section-list-cis-service-plans-examples" "> --> Examples List CIS services plans. ibmcloud cis plans --refresh
<-- </section "id="section-list-cis-service-plans-examples" "> --><-- </section "id="section-list-cis-service-plans" "> --><-- </section "id="section-resource-instance" "> --><-- <section "id="section-routing" "> --> Routing Manipulate routing by using the following routing commands.<-- <section "id="section-show-routing" "> --> ibmcloud cis routing Get details of Routing settings (Enterprise plan only). ibmcloud cis routing DNS_DOMAIN_ID (--smart-routing | --tiered-caching) -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-show-routinge-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.--smart-routing: Leverages real-time network intelligence to route traffic across paths from the origin to a CIS data center.--tiered-caching: Uses regional Tier 1 CIS data centers to accelerate content delivery.-i, --instance: Instance name or ID.
"id": "b7246cdf-892a-4a6c-8fa9-491a5f585bd0",
"created_on": "2019-09-11 13:46:51.68793557 +0000 UTC",
"modified_on": "2019-09-11 13:46:51.68793557 +0000 UTC",
"permitted_network": {
"vpc_crn": "crn:v1:staging:public:is:us-east:a/0821fa9f9ebcc7b7c9a0d6e9bf9442a4::vpc:b7246cdf-892a-4a6c-8fa9-491a5f585bd0"
},
"type": "vpc",
"state": "REMOVAL_IN_PROGRESS"
}

Removing a permitted network can take up to 5 minutes. You cannot add the VPC back to the DNS zone's permitted network until the removal operation is complete.









 Using the CLI 

First use the ibmcloud dns instance-target command to set the target operating DNS Services instance.

$ ibmcloud dns instances
Retrieving service instances for service 'dns-svcs' ...
OK

Name ID Location State Service Name
DNS Services-km ffffffff-b042-41fd-885e-000000000000 global active dns-svcs

$ ibmcloud dns instance-target "DNS Services-km"

Store the zone ID in a variable so you can use it in the following commands without having to type it every time. For example, to store the zone ID in a variable, run this command:

DNS_ZONE_ID="example.com:f7f40364-a5e6-48f7-9fc9-387434c579ae"



 Adding permitted networks
ibmcloud cis security-events DNS_DOMAIN_ID --ip-class IP_CLASS] --method METHOD] --scheme SCHEME] --ip IP_ADDR] --host HOSTNAME] --protocol PROTOCOL] --uri URI] --ua USER_AGENT] --colo COLO] --ray-id RAY_ID] --kind KIND] --action ACTION] --cursor CURSOR] --country COUNTRY] --since START_DATE] --until END_DATE] --source SOURCE] --limit LIMIT] --rule_id RULE_ID] -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! ! ! !
<-- <section "id="section-list-security-event-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.--ip-class: IP class is a map of client IP to visitor classification. Valid values: unknown, clean, badHost, searchEngine, whitelist, greylist, monitoringService, securityScanner, noRecord, scan, backupService, mobilePlatform, tor.--method: The HTTP method of the request. Valid values: GET, POST, DELETE, PUT, HEAD, PURGE, OPTIONS, PROPFIND, MKCOL, PATCH, ACL, BCOPY, BDELETE, BMOVE, BPROPFIND, BPROPPATCH, CHECKIN, CHECKOUT, CONNECT, COPY, LABEL, LOCK, MERGE, MKACTIVITY, MKWORKSPACE, MOVE, NOTIFY, ORDERPATCH, POLL, PROPPATCH, REPORT, SEARCH, SUBSCRIBE, TRACE, UNCHECKOUT, UNLOCK, UNSUBSCRIBE, UPDATE, VERSION-CONTROL, BASELINE-CONTROL, X-MS-ENUMATTS, RPC_OUT_DATA, RPC_IN_DATA, JSON, COOK, TRACK.--scheme: The scheme of the uri.
Deprecated] ibmcloud cis range-app-update DNS_DOMAIN_ID APP_ID -j JSON_FILE -i, --instance INSTANCE] --output FORMAT] ! !!!!!!!!!!!!
<-- <section "id="section-update-range-app-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.APP_ID: The ID of range application. Required.--name: The name of DNS record for the range application.--add-origin-direct: Add new destination addresses to origin.--remove-origin-direct: Remove destination addresses from origin.--origin-direct: Destination addresses to the origin.--origin-lb-name: The Load Balancer name associated with the range application.--origin-lb-port: The Load Balancer port associated with the range application. The default value is 22.--proxy-protocol: Enable Proxy Protocol to the origin. Valid values: on, off, v1, v2, simple. The default value is off. Deprecated. The value on is equivalent to v1.--ip-firewall: Control whether or not enables the IP Firewall for this application. Valid values: on, off. The default value is off.--edge-connectivity: The IP versions supported for inbound connections on range anycast IPs. Valid values: all, ipv4, ipv6. The default value is all.--edge-tls: The type of TLS termination associated with the application. Valid values: off, flexible, full, strict. The default value is off.--traffic-type: Determines how data travels from the edge to your origin. Valid values: direct, http, https. The default value is direct.--json: The JSON file or JSON string used to describe a range application.
<-- <ul> -->

* The required fields in JSON data are protocol, dns.

<-- <ul> -->

* protocol: Port configuration at CIS's edge.
[Permitted network link to VPC overview page](https://cloud.ibm.com/docs-content/v1/content/d56dbd8ab7d14086029681ee71679e14aea53723/dns-svcs/images/permit-net-nav.svg)

Figure 1. Navigating to an IBM VPC from permitted networks section





 List permitted networks 



1. Select the desired zone from the table on the DNS Zones page.
2. Select the Permitted Networks tab.



Zoom

![Cross-account filter example](https://cloud.ibm.com/docs-content/v1/content/d56dbd8ab7d14086029681ee71679e14aea53723/dns-svcs/images/cross-account-list.png)

Figure 2. Filter by cross-account ACL account ID

By default,the list contains permitted networks that were added from your account as the owner. To see permitted networks added by cross-account ACL users, you can use a filter by selecting the account IDs.

You can select a maximum of 5 cross-account IDs.





 Removing a permitted network 

From the permitted networks table, click the Delete icon. Confirm the delete process in the dialog box that appears.

If a network exists in a zone, you cannot delete the zone until the permitted network is deleted.







 Using the API 

First store the API endpoint in a variable so you can use it in API requests without having to type the full URL. For example, to store the production endpoint in a variable, run this command:

DNSSVCS_ENDPOINT=https://api.dns-svcs.cloud.ibm.com

To verify that this variable was saved, run echo $DNSSVCS_ENDPOINT and make sure the response is not empty.



 Adding permitted networks 

A DNS zone's initial state is PENDING_NETWORK_ADD, because its permitted network list is empty when the DNS zone is created.
It can take up to 15 - 30 minutes for the update to take effect. Check with your DNS provider to obtain an accurate time estimate.
* How do I add a CNAME record for my CDN domain in DNS?

In your DNS configuration page for your CDN domain, you can create a CNAME record with the CDN domain name as the Host, and the IBM CNAME you used to configure the CDN as the CNAME. The IBM CNAME ends with cdn.appdomain.cloud..

A typical CNAME record looks similar to the following on the DNS configuration page:



CNAME record example

 Resource Type Host Points to (CNAME) TTL 

 CNAME www.example.com example.cdn.appdomain.cloud 15 minutes 



* When am I billed for my CDN?

IBM Cloud Content Delivery Network billing occurs according to the billing period established in your IBM Cloud account.
* If I select Delete from the Overflow menu, does that delete my account?

No, if you select 'Delete' from the Overflow ![Overflow menu](https://cloud.ibm.com/images/overflow.png) menu, only that CDN is deleted. Your account still exists, and you can create additional CDNs.
* Does content caching use push or pull?

Content caching is done using an origin pull model. Origin Pull is a method by which data is "pulled" by the Edge server from the origin server, as opposed to manually uploading the content onto the Edge server.
* Is there a recommended browser to use for CDN service configuration?

Yes, Firefox and Chrome are the recommended browsers. It is recommended that you use the latest versions with your IBM Cloud Content Delivery Network.
* What is the purpose of providing a path when creating my CDN?

If you provide a path while creating your CDN, it allows you to isolate the files that can be served through CDN from a particular origin server.
* My CDN is in an Error State. What do I do now?
Deprecated] ibmcloud cis range-app-create DNS_DOMAIN_ID -j JSON_FILE -i, --instance INSTANCE] --output FORMAT] ! !!!!!!!!!!!!
Show more
<-- <section "id="section-create-range-app-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.--name: The name of DNS record for the range application.--edge-port: Port configuration at CIS's edge. The default value is 22.--origin-direct: Destination addresses to the origin.--origin-lb-name: The Load Balancer name associated with the range application.--origin-lb-port: The Load Balancer port associated with the range application. The default value is 22.--protocol: Protocol type. Valid values: tcp, udp. UDP protocol support is in early access, request custom UDP from CIS dashboard before creating range UDP app. The default value is tcp.--proxy-protocol: Enable Proxy Protocol to the origin. Valid values: on, off, v1, v2, simple. The default value is off. Deprecated. The value on is equivalent to v1.--ip-firewall: Control whether or not enables the IP Firewall for this application. Valid values: on, off. The default value is off.--edge-connectivity: The IP versions supported for inbound connections on range anycast IPs. Valid values: all, ipv4, ipv6. The default value is all.--edge-tls: The type of TLS termination associated with the application. Valid values: off, flexible, full, strict. The default value is off.--traffic-type: Determines how data travels from the edge to your origin. Valid values: direct, http, https. The default value is direct.--json: The JSON file or JSON string used to describe a range application.
<-- <ul> -->

* The required fields in JSON data are protocol, dns.
address 192.0.2.2
netmask 255.255.255.248
gateway 192.0.2.1

auto eth0
iface eth0 inet static
address 10.0.0.2
netmask 255.255.255.248

Static route for backend service network
up route add -net 10.0.0.0/8 gw 10.0.0.1



DNS Configuration

The primary and secondary DNS configuration is contained in a separate file. You need to edit this configuration file with the following information. If this virtual machine does not have access to the private network, you need to replace the server IPs with the IP addresses of the DNS servers that you want to use.



* /etc/resolv.conf nameserver 10.0.80.11 nameserver 10.0.80.12



For these changes to take effect, you want to restart networking on the server. You can restart the network by running the following command:



* /etc/init.d/network restart



Note: 192.0.2.0/24 is used as Public IP Documentation per RFC1166 and RFC5737. You do not use these IP addresses on your servers.
DNS API 

Users can interact with the IBM Cloud authoritative DNS servers through the SoftLayer_Dns_Domain service.

Each SoftLayer_Dns_Domain has a collection of SoftLayer_DNS_Domain_ResourceRecords referenced by the resourceRecords relational property. It is possible to interact with resource records through the SoftLayer_Dns_Domain service; however, it is best to use the SoftLayer_Dns_Domain_ResourceRecord service directly after initial zone creation.



 Domains 



 List domains 

A list of all domains currently hosted on the IBM Cloud name servers can be retrieved with SoftLayer_Account::getDomains returns an array of SoftLayer_Dns_Domain template objects. You can extend this call to also pull the records that are associated with these domains using an object mask.

$client = SoftLayer_SoapClient::getClient('SoftLayer_Account', null, $apiUser, $apiKey);
$objectMask = "mask.resourceRecords";
$client->setObjectMask($objectMask);
$domains = $client->getDomains();
print_r($domains);





 Create domains 

To create a new zone, a SoftLayer_Dns_Domain template object must be created and passed into SoftLayer_Dns_Domain::createObject. NS records for ns1.softlayer.com and ns2.softlayer.com are automatically added during creation. Include at least one A or AAAA record with the template object for successful creation. Domain serial numbers are added or updated by the API so there is no need to include them in the template object.

The following properties are necessary when creating a SoftLayer_Dns_Domain object.



* name: Domain name including the TDL
* resourceRecords: An array of at least one SoftLayer_Dns_Domain_ResourceRecord



$client = SoftLayer_SoapClient::getClient('SoftLayer_Dns_Domain', null, $apiUser, $apiKey);
$template = new stdClass();
* If you are the site owner, review CIS Rate Limiting thresholds and adjust your Rate Limiting configuration.
* If your Rate Limiting blocks requests in a short time period (for instance, 1 second) try increasing the time period to 10 seconds.



For guidance on when you expect a new Edge function to exceed rate limits, see [Working wiht Edge functions](https://cloud.ibm.com/docs/cis?topic=cis-working-with-edge-functions).







 Error 1016: Origin DNS error 

Error 1016 occurs when CIS cannot resolve the origin web server’s IP address.

Common causes for Error 1016 are:



* A missing DNS A record that mentions origin IP address.
* A CNAME record in the CIS DNS points to an unresolvable external domain.
* The origin host names (CNAMEs) in your CIS Load Balancer default, region, and fallback pools are unresolvable. Use a fallback pool configured with an origin IP as a backup in case all other pools are unavailable.
* When creating a Range app with a CNAME origin, you need first to create a CNAME on the CIS DNS side that points to the origin.





 Resolution 

To resolve an error 1016:



* Verify your CIS DNS settings include an A record that points to a valid IP address that resolves via a DNS lookup tool.
* For a CNAME record pointing to a different domain, ensure that the target domain resolves via a DNS lookup tool.









 Error 1018: Could not find host 

Common causes of an 1018 error are:



* The CIS domain was recently activated and there is a delay propagating the domain’s settings to the CIS edge network.
* The CIS domain was created via a CIS partner (for example, a hosting provider) and the provider's DNS failed.



Error 1018 is returned via an HTTP 409 response code.



 Resolution 

Contact Support with the following details:



* Your domain name
* A screenshot of the 1018 error including the RayID mentioned in the error message
* The time and timezone the 1018 error occurred









 Error 1019: Compute server error
In this example vmware.ibmcloud.local is used, but you may modify this to fit your needs.

VMWARE_DNS_ZONE_NAME=vmware.ibmcloud.local

VMWARE_DNS_ZONE=$(ibmcloud dns zone-create $VMWARE_DNS_ZONE_NAME -d "Zone for VMware on VPC" --output json | jq -r .id)
2. Add your previously created IBM Cloud VPC in the permitted networks. Use the IBM Cloud VPC CRN here.

ibmcloud dns permitted-network-add $VMWARE_DNS_ZONE --vpc-crn $VMWARE_VPC_CRN







 Step 3: Creating DNS records 

DNS records for the ESXi hosts will be created after they will be provisioned in the [next tutorial](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-bmsvpc-bm-vmware-bms) following the commands provided below.



1. To create DNS records via CLI, the following command provides a help for record creation.

ibmcloud dns resource-record-create --help
2. To create A records for your previously created Zone vmware.ibmcloud.local, you can use the following CLI command (modify the 'NAME' and 'IP_ADDRESS' accordingly):

ibmcloud dns resource-record-create $VMWARE_DNS_ZONE --type A --name NAME --ipv4 IP_ADDRESS







 Step 4: Validate DNS records 



1. List information about configured zones in your DNS instance dns-vmware. Use the following command.

ibmcloud dns zones -i dns-vmware
2. List information about configured records in your DNS instance dns-vmware and zone vmware.ibmcloud.local. Use the following command.
--ipv4
: IPv4 address.

--ipv6
: IPv6 address.

--cname
: Canonical name.

--ptrdname
: Hostname of the relevant A or AAAA record.

--text
: Human readable text.

--exchange
: Hostname of Exchange server.

--preference
: Preference of the MX record

--service
: The symbolic name of the desired service, beginning with an underscore _.

--protocol
: The symbolic name of the desired protocol.

--port
: Port number of the target server.

--weight
: Weight of distributing queries among multiple target servers.

--priority
: Priority of the SRV record.

--target
: Hostname of the target server.

--ttl
: Time to live, in seconds. Default value is 900. Valid values: 60, 120, 300, 600, 900, 1800, 3600, 7200, 18000, 43200.

-r, --record-content
: The JSON file or JSON string used to describe a DNS Resource Record. See [Required fields for -r --record-content](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-dns-services-cli-commandsrequired-fields-r-record-content) for more detail.

-i, --instance value
: > Instance name or ID. If not set, the context instance specified by dns instance-target INSTANCE is used.

--output value
: Specify output format. Currently, json is the only supported format.





 Required fields for -r --record-content 

The required field in JSON data is type.

Resource record type. Valid values: A, AAAA, CNAME, PTR, TXT, MX, SRV.



* For type A, AAAA: Extra required fields are name, rdata.



* name: Resource record name.
Managing reverse or PTR (Pointer) records 

PTR, or pointer, records resolve IP addresses into hostnames. Users can add PTR records to be associated with an IP address by using Reverse Records. Also, PTR records can be edited in the same way they are added. Follow these steps to add or edit a PTR record for a device.

Have the public IP address for the device that will receive the PTR record ready.



1.  From your browser, open the [IBM Cloud® console](https://cloud.ibm.com/) and log in to your account.
2.  Select the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg), then click Classic Infrastructure.
3.  From the Classic Infrastructure menu, select Network > DNS > Reverse Records to open the Reverse DNS Records page.
4.  Enter the public IP address of the device in the View IP field.
5.  Complete or update the fields for the record based on the following:



*  Hostname: The hostname to which the IP address resolves.
*  Reverse TTL: The time to live (TTL) for the new record.



6.  Click the Save button to save the record.



You can also choose Edit RDNS for all IPs in this Subnet to make changes across the entire subnet. To remove details from the PTR record, delete all information from the fields and click the Save button.
When you add a subdomain to CIS, you are given two name servers to configure, as usual. You configure a Name Server (NS) record for each of the two name servers as DNS records within your domain being managed by the other DNS provider. When we are able to verify that the required NS records have been added, we activate your subdomain. If you do not manage the higher level domain within your organization, you must work with the owner of the higher level domain to get the NS records added.





 What are the defaults for DNS TTL? 

The following are defaults for DNS time-to-live (TTL), in seconds.



* For records such as A record, CNAME, and so on, the automatic TTL is 300s.







 What is TLS? 

TLS is a standard security protocol for establishing encrypted links between a web server and a browser in an online communication. A TLS certificate is necessary to create a TLS connection with a website and comprises the domain name, the name of the company, and additional data, such as company address, city, state, and country. The certificate also shows the expiration date and details of the issuing Certificate Authority (CA).





 How Does TLS Work? 

When a browser initiates a connection with a TLS secured website, it first retrieves the site's TLS Certificate to check whether the certificate is still valid. It verifies that the CA is one that the browser trusts, and that the certificate is being used by the website for which it has been issued. If any of these checks fail, you'll get a warning indicating that the website is not secured by a valid certificate.

When a TLS certificate is installed on a web server, it enables a secure connection between the web server and the browser that connects to it. The website's URL is prefixed with "HTTPS" instead of "HTTP" and a padlock is shown on the address bar. If the website uses an extended validation (EV) certificate, the browser might also show a green address bar.





 Why do I see a privacy warning?
--file
: BIND zone file to import. Support type: A, AAAA, CNAME, MX, PTR, SRV, TXT.

-i, --instance
: Instance name or ID. If not set, the context instance specified by dns instance-target INSTANCE is used.

--output
: Specify output format. Currently, json is the only supported format.





 Examples 

Import resource records from BIND zone file dns_records.cfg in zone f1d596fc-7e86-4b99-b912-9508167e9e56 for instance dns-demo.

ibmcloud dns resource-records-import f1d596fc-7e86-4b99-b912-9508167e9e56 --file dns_records.cfg -i "dns-demo"







 ibmcloud dns resource-records-export 

Export resource records to BIND zone file.

ibmcloud dns resource-records-export DNS_ZONE_ID [--file FILE] [-i, --instance INSTANCE_NAME | INSTANCE_ID] [--output FORMAT]



 Command options 

DNS_ZONE_ID
: The ID of DNS zone.

--file
: The BIND zone file that saves the exported resource records.

-i, --instance
: Instance name or ID. If not set, the context instance specified by dns instance-target INSTANCE is used.

--output
: Specify output format. Currently, json is the only supported format.





 Examples 

Export resource records in zone f1d596fc-7e86-4b99-b912-9508167e9e56 to zone file dns_records.cfg for instance dns-demo.

ibmcloud dns resource-records-export f1d596fc-7e86-4b99-b912-9508167e9e56 --file dns_records.cfg -i "dns-demo"









 Global load balancer 

Manage global load balancers by using the following glb commands.