vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Domain lifecycle concepts 

Domains configured in CIS begin in pending state, and become active after the authoritative name servers assigned to the domain are configured correctly at the DNS provider or registrar.

The following diagram shows a sample domain lifecycle, with labels that correspond to the list of domain state transitions.

Zoom

![Diagram of domain lifecycle](https://cloud.ibm.com/docs-content/v1/content/cb1eb27836421578019401fa7556779109430b29/cis/images/domain-lifecycle-lt.png)

Figure 1. Domain lifecycle

Domain state transitions:



1. Adding a domain to a CIS instance puts the domain in pending state. Authoritative name servers are assigned but have not yet been configured at the DNS provider or registrar.
2. Configuring name server records for the authoritative name servers of the domain at the DNS provider or registrar activates the domain.
3. (Enterprise only) Deleting the domain marks the domain as Deletion pending. An Enterprise plan level domain will not be deleted immediately and can take up to 24 hours to actually be removed.
4. (Enterprise only) After a period of time, the domain is deleted.
5. (Standard) A Standard plan level instance can be deleted immediately.
6. The name server configuration of a domain is monitored. A change to the configuration of the authoritative name server at the DNS provider or registrar marks the domain moved. This can be the result of an update to the name servers if the domain is moved to a different CIS instance, or it can be a sign of a bad name server configuration.

A moved domain might stop serving traffic, and could potentially be deleted. If your domain is in moved state and you believe this is in error, [contact IBM Support](https://cloud.ibm.com/docs/cis?topic=cis-gettinghelp).
7. Moved domains could potentially be deleted automatically, or by the user.





 Domain lifecycle states 

You may encounter any of the following domain lifecycle states:
Because CIS doesn't support email traffic by default, you must set the PTR record to the location of your email server. Contact your email provider for assistance.







 Updating DNS records 

In each record row, you can click the Edit record option from the menu, which opens a dialog box that you can use to update the record.

After you are finished making your changes, select Update record to save them, or Cancel to abort the changes.





 Deleting DNS records 

In each record row, you can select the Delete record option from the menu, which opens a dialog box to confirm the delete process.

You can select the Delete button to confirm your delete action. Select Cancel if you don't want to delete.





 Importing and exporting DNS records 

DNS records can be imported into and exported from CIS. All files are imported and exported as .txt files in BIND format. Learn more about [BIND format](https://en.wikipedia.org/wiki/Zone_file). Click the overflow menu and select to import or export records.

Import records - By default, a total of 3500 DNS records are allowed (imported and created on CIS). You can import multiple files, one at a time, as long as the total number of records is under the max limit. After importing, you are shown a summary with the number of records successfully added and the number that failed, along with the reason why each record failed.

Export records - Use Export records to create a backup of your zone file, or export it to use with another DNS provider. When this menu option is clicked, the records are downloaded to the location specified by your browser settings (typically the Downloads folder). To select another folder location, change your browser's settings to prompt you for a location with each download.





 Configuring and managing your secure DNS 

DNSSec is a technology to digitally sign DNS data so you can be assured it is valid. To eliminate vulnerability from the internet, DNSSec must be deployed at each step in the lookup, from root zone to final domain name (for example, www.icann.org).
* UI
* CLI
* API







 Deleting a VPC and its associated resources 

Before you can delete an IBM Cloud® Virtual Private Cloud in the IBM Cloud console, you must delete all of the VPC's public gateways, subnets, and attached resources.



 Deleting a VPC by using the IBM Cloud console 

To delete a VPC by using the console:



1. Find all subnets in the VPC. Click VPCs in the navigation pane and select your VPC.
2. On the VPC details page, go to the Subnets in this VPC list and select a subnet to view its details.
3. Delete any resources that are attached to the subnet. In the navigation pane, click Attached resources. Select each attached instance, load balancer, and VPN gateway to go its details page and click the delete icon. Attached instances must be stopped before you can delete them.

Although the resource's status immediately changes to Deleting, it can take up to 30 minutes for the delete operation to complete. The subnet can't be deleted until all attached resources are no longer displayed in the console.
4. After all attached resources are deleted, go back to the subnet's details page, and click the delete icon.
5. After you delete all subnets, go back to the details page for the VPC, and click the delete icon. The VPC and any public gateways are deleted.







 Deleting a VPC by using the IBM Cloud CLI 

The following examples show how to delete resources from your IBM Cloud® Virtual Private Cloud, for every VPC resource, in the suggested order.

The following key facts are important to remember about deletion:



* A VPC cannot be deleted until it is empty.
* All containing resources must be deleted successfully before the parent resource can be deleted.
* If the resource is pending a deletion, it shows a deleting status when viewed in list queries.
If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-show-glb-monitor-options" "> --><-- <section "id="section-show-glb-monitor-examples" "> --> Examples Show the details of GLB monitor f1aba936b94213e5b8dca0c0dbf1f9cc. ibmcloud cis glb-monitor f1aba936b94213e5b8dca0c0dbf1f9cc -i "cis-demo"
<-- </section "id="section-show-glb-monitor-examples" "> --><-- </section "id="section-show-glb-monitor" "> --><-- <section "id="section-delete-glb-monitor" "> --> ibmcloud cis glb-monitor-delete Delete the GLB monitor for a given service instance. ibmcloud cis glb-monitor-delete GLB_MON_ID -i, --instance INSTANCE] ! ! ! ! ! !
<-- <section "id="section-delete-glb-monitor-options" "> --> Command options GLB_MON_ID: The ID of global load balancer monitor. Required.-i, --instance: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.<-- </section "id="section-delete-glb-monitor-options" "> --><-- <section "id="section-delete-glb-monitor-examples" "> --> Examples Delete GLB monitor f1aba936b94213e5b8dca0c0dbf1f9cc. ibmcloud cis glb-monitor-delete f1aba936b94213e5b8dca0c0dbf1f9cc -i "cis-demo"
ibmcloud cis domain-pause 31984fea73a15b45779fa0df4ef62f9b -i "cis-demo"







 ibmcloud cis domain 

Display the given domain details.

ibmcloud cis domain DNS_DOMAIN_ID [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

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

--output
: Specify output format, only JSON is supported.





 Examples 

Display the specified domain details.

ibmcloud cis domain 31984fea73a15b45779fa0df4ef62f9b -i "cis-demo"







 ibmcloud cis domain-remove 

Remove a given domain.

ibmcloud cis domain-remove DNS_DOMAIN_ID [-i, --instance INSTANCE]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

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





 Examples 

Remove the specified domain.

ibmcloud cis domain-remove 31984fea73a15b45779fa0df4ef62f9b -i "cis-demo"







 ibmcloud cis domains 

List domains for a given service instance.

ibmcloud cis domains [--instance INSTANCE_NAME] [--output FORMAT]



 Command options 

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

--output
: Specify output format, only JSON is supported.





 Examples 

List domains for the specified domain cis-demo.

ibmcloud cis domains -i "cis-demo"







 ibmcloud cis domain-activation-check
* SHA-1/RSA signed certificate using RSA 2048-bit key.



CIS can issue for all TLDs except for .cu, .iq, .ir, .kp, .sd, .ss, and .ye. CIS manages the expiration date. To edit the hostnames on your dedicated custom certificate, you must reorder then delete. For example, you order a dedicated custom certificate with the hostname alpha.yourdomain.com. To add the hostname beta.yourdomain.com to your dedicated custom certificate, order another dedicated custom certificate with the hostnames alpha.yourdomain.com and beta.yourdomain.com. Afterwards you must delete the original dedicated custom certificate.

The first time you order a dedicated certificate Domain Control Validation (DCV) process occurs, which generates a corresponding TXT record. If you delete the TXT record, the DCV process happens again when you order another dedicated certificate. If you delete a dedicated certificate, the TXT record corresponding to the DCV process is not deleted.

The following are common errors seen when ordering dedicated certificates:



* Error connecting to certificate service.
* Error while requesting from certificate service.



If you receive an error when ordering certificates, refresh the page and try again.





 Use a provisioned certificate 

IBM has partnered with several Certificate Authorities (CAs) to provide domain wildcard certificates for our customers. Manual verification could be required for setting up these certificates. Your support team can help you perform these additional steps.





 Certificate priority at our edge 

The priority by which the certificates are displayed at our edge is:



1. Uploaded custom
2. Dedicated custom
3. Dedicated wildcard
4. Universal







 Minimum TLS version 

See [Minimum TLS version](https://cloud.ibm.com/docs/cis?topic=cis-cis-tls-optionsminimum-tls-version). Higher levels of TLS provide more security, but might prevent customers from connecting to your site.
hpvs instance-delete 

This command deletes a Hyper Protect Virtual Servers.

ibmcloud hpvs instance-delete (NAME | CRN)



 Command options 

NAME
: The name of your new instance. An error message is displayed if you specify a NAME that is not unique, for example,

VS name 'ABC' is ambiguous: more than one VS exist for the provided name: [crn1 crn2].

Specify the CRN if your instance name is not unique.

CRN
: The server's Cloud resource name (CRN). Specify the CRN if NAME is not unique. You can run the ibmcloud hpvs instances command to get the CRN.

--force
: Forces the deletion of the Hyper Protect Virtual Servers instance without prompting for confirmation.





 Example output 

Are you sure you want to delete the service instance? [y/N]> y

Deleting service instance crn:v1:staging:public:hpvs:dal13:a/1075962b93044362a562c8deebbfba2e:231fbbf4-1415-4162-86f0-9d50c260106d:: ...

OK
Service instance 'crn:v1:staging:public:hpvs:dal13:a/1075962b93044362a562c8deebbfba2e:231fbbf4-1415-4162-86f0-9d50c260106d::' was deleted.
You can restore a resource within 7 days after you delete it.
You can run the 'ibmcloud resource reclamations' command to check the resources that you can restore.
To irrecoverable delete the instance run the 'ibmcloud resource reclamation-delete RECLAMATION_ID' command.

When you delete a virtual server from the resource list, the server isn't deleted immediately, it stops and is marked for deletion. It is deleted after a reclamation period of seven days.
: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.

--output
: Specify output format, only JSON is supported.





 Examples 

Add a new domain test.com in instance cis-demo.

ibmcloud cis domain-add "test.com" -i "cis-demo"







 ibmcloud cis domain-resume 

Resume the given domain.

ibmcloud cis domain-resume DNS_DOMAIN_ID [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

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

--output
: Specify output format, only JSON is supported.





 Examples 

Resume the specified domain.

ibmcloud cis domain-resume 31984fea73a15b45779fa0df4ef62f9b -i "cis-demo"







 ibmcloud cis domain-pause 

Pause the given domain.

ibmcloud cis domain-pause DNS_DOMAIN_ID [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

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

--output
: Specify output format, only JSON is supported.





 Examples 

Pause the specified domain.

ibmcloud cis domain-pause 31984fea73a15b45779fa0df4ef62f9b -i "cis-demo"







 ibmcloud cis domain 

Display the given domain details.

ibmcloud cis domain DNS_DOMAIN_ID [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.
* For more information on deleting a subnet, see [Deleting VPC resources by using the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-deleting-using-console), [Deleting VPC resources by using the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-deleting-using-cli), or [Deleting VPC resources by using the API](https://cloud.ibm.com/docs/vpc?topic=vpc-deleting-using-api).



* floating-ip



* For more information on creating a floating IP, see [Using the IBM Cloud console to create VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-the-ibm-cloud-console), [Using the REST APIs to create VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-the-rest-apis), or [Using the CLI to create VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-clicreate-a-subnet-cli).
* For more information on deleting a floating IP, see [Deleting VPC resources by using the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-deleting-using-console), [Deleting VPC resources by using the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-deleting-using-cli), or [Deleting VPC resources by using the API](https://cloud.ibm.com/docs/vpc?topic=vpc-deleting-using-api).



* network-acl
Deleting ESXi servers from vCenter Server instances 

You can contract the capacity of your VMware vCenter Server® instance according to your business needs by deleting VMware ESXi™ servers.



 Before you delete ESXi servers from vCenter Server instances 



* Deleting ESXi servers from vCenter Server instances with VMware vSphere® 6 is not supported.
* For the gateway cluster, you cannot add or delete ESXi servers.
* Whenever possible, remove ESXi servers by using the IBM Cloud® for VMware Solutions console because changes that you make on the VMware vSphere® Web Client are not synchronized with the IBM Cloud for VMware Solutions console. Therefore, remove ESXi servers from vCenter Server only for on-premises ESXi servers or ESXi servers that you don't manage in the IBM Cloud for VMware Solutions console.
* When you delete ESXi servers, the servers are placed in maintenance mode, and then, all the virtual machines (VMs) running on the servers are migrated before they are deleted from vCenter Server. For maximum of control over the relocation of VMs, place the ESXi servers in maintenance mode and migrate the VMs running on them manually using the VMware vSphere Web Client. After that, delete the ESXi servers by using the VMware Solutions console.
* If you are using NFS storage, NSX-T™ instances require at least three ESXi servers for a consolidated cluster or at least two servers for any other cluster. NSX-V instances require at least two ESXi servers.
* If you are using vSAN storage, at least four ESXi servers are required.
* (NSX-V only) If F5® BIG-IP® or FortiGate® Virtual Appliance is installed on your ESXi server, you must migrate the F5 BIG-IP and FortiGate VMs to a different ESXi server than the one that is hosting the VMs.
* (NSX-V only) If IBM Spectrum® Protect Plus is installed on your ESXi server, ensure that there are no active (failed or in progress) backup or restore operations. These active operations might prevent the ESXi server from being deleted.







 Procedure to delete ESXi servers from vCenter Server instances
Deleting a CDN 

To delete a CDN, follow these steps:



1.  Click Delete from the Overflow ![Overflow menu](https://cloud.ibm.com/docs-content/v1/content/006fd22ab2811b7d19804c763a00568b3da4c03a/CDN/images/overflow.png) menu. A confirmation window appears.
2.  Click Delete to proceed.
3.  When the delete process is complete, click Get status from the Overflow menu to remove the row from the CDN list. If the delete process has not completed, this action has no effect.





  FAQs for deleting CDN 



  Will deleting a CDN also delete my account? 

No. Selecting Delete deletes only the CDN; it does not delete your account.





  Why is the DV SAN certificate CDN still there after I deleted it? 

If your CDN is configured with HTTPS with DV SAN certificate, it can take up to 5 hours to complete the deletion process.





  Why did the deletion of the DV SAN certificate domain fail? It shows that the domain is still live on the network. 

If your CDN is configured with DV SAN certificate HTTPS, you must remove the DNS record that points your domain to the [IBM CNAME](https://cloud.ibm.com/docs/CDN?topic=CDN-next-steps-after-orderingibm-cname) before deleting your CDN. Otherwise, the deletion fails with the error message 'Delete CDN failed: the xxxxxx is still live on network, please remove the DNS record pointing to Akamai.'

If you already deleted the DNS record that points your domain to the [IBM CNAME](https://cloud.ibm.com/docs/CDN?topic=CDN-next-steps-after-orderingibm-cname) and you still get an error, wait 15 - 30 minutes for the DNS update to take effect.
Optional: Unbind or delete a service instance.

You might want to unbind or delete a service instance when it is no longer used or when you want to free up some spaces. To unbind a service instance from your app, use the ibmcloud cf unbind-service command. To delete a service instance, use the ibmcloud cf delete-service command.

For more information about services, see Services. For more information about the ibmcloud cf options that you can use to manage your apps in the IBM Cloud environment, run ibmcloud cf --help in the ibmcloud cf command line interface.

Make sure you no longer require a service instance before you delete it. Deleting a service instance erases all data that is associated with that instance of the service. Any app that is bound to a deleted service cannot have its <VCAP_SERVICES> environment variable updated until the app is restarted.









 Calculating your app cost 

If your 30-day free trial has expired, and you want to continue to use IBM Cloud, you must add your credit card information for a Pay As You Go account or a Subscription account. However, IBM Cloud still provides free allowances for the community runtime frameworks (Python, PHP, Go, Ruby, Tomcat) and services even after you convert to a pay account. You are not charged by IBM Cloud unless the usage is beyond the free allowances.

IBM Cloud provides an estimator and calculator for you to see your app cost. You can see the cost of your app in the following ways:

In your console, click your app. Then, in the Overview page, click estimate the cost of this app to see the price of SDK for Node.js runtime and Support, and the total monthly price of your app.

Or, in the Pricing Sheet page, type the monthly usage of the runtime and services of your app. For example, 3 instances of SDK for Node.js with 1 GB memory for each instance. The monthly price is calculated and displayed.

You can also calculate your app cost manually by adding up the prices of your runtimes and services and deducting the free allowance. For more information, see Calculating your costs manually.
Update access certificate a5836c2a7ea72d2e225890caea70ae32.

ibmcloud cis access-certificate-update 31984fea73a15b45779fa0df4ef62f9b a5836c2a7ea72d2e225890caea70ae32 --name example --associated-hostnames example.com -i cis-demo







 ibmcloud cis access-certificate-delete 

Delete an access certificate (Enterprise plan only).

ibmcloud cis access-certificate-delete DNS_DOMAIN_ID ACCESS_CERTIFICATE_ID [-i, --instance INSTANCE]

Must clear the associated hostnames before deleting the certificate.



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

ACCESS_CERTIFICATE_ID
: The ID of access certificate. Required.

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





 Examples 

Delete access certificate a5836c2a7ea72d2e225890caea70ae32.

ibmcloud cis access-certificate-delete 31984fea73a15b45779fa0df4ef62f9b a5836c2a7ea72d2e225890caea70ae32 -i cis-demo







 ibmcloud cis access-certificates-settings 

Get access certificates settings for a given DNS domain (Enterprise plan only).

ibmcloud cis access-certificates-settings DNS_DOMAIN_ID [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

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

--output
: Specify output format, only JSON is supported.





 Examples
* (NSX-V only) If F5® BIG-IP® or FortiGate® Virtual Appliance is installed on your ESXi server, you must migrate the F5 BIG-IP and FortiGate VMs to a different ESXi server than the one that is hosting the VMs.
* (NSX-V only) If IBM Spectrum® Protect Plus is installed on your ESXi server, ensure that there are no active (failed or in progress) backup or restore operations. These active operations might prevent the ESXi server from being deleted.







 Procedure to delete ESXi servers from vCenter Server instances 



1. From the IBM Cloud for VMware Solutions console, click Resources > vCenter Server from the left navigation pane.
2. In the vCenter Server instances table, click the instance for which you want to contract capacity.
3. Click the Infrastructure tab.
4. In the applicable cluster table, click the cluster from which you want to delete ESXi servers.
5. In the ESXi servers section, select the servers that you want to delete and click Delete.
6. Click Delete in the Delete ESXi server window.







 Results after you delete ESXi servers from vCenter Server instances 



1. You might experience a slight delay on the console, while the instance status changes from Available to Modifying. Allow the operation to complete before you make more changes to the instance.
2. You are notified by email that your request to delete ESXi servers is being processed. On the console, the status of the cluster that is associated with the ESXi servers is changed to Modifying.
3. The ESXi servers are fully reclaimed by IBM Cloud infrastructure at the end of the IBM Cloud infrastructure billing cycle, which is typically 30 days.

You are billed until the end of the IBM Cloud infrastructure billing cycle for the deleted ESXi servers.







 Related links 



* [vCenter Server BOM](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_bom)