vania-janet/multiturn-rag-retrieval-data huggingface dataset:
To renew a registration for an existing domain, select [Classic Infrastructure](https://%7BDomainName%7D/gen1/infrastructure/devices) from the menu in the IBM Cloud console, and then go to Services > Domain Registration. See [Renewing existing domains](https://cloud.ibm.com/docs/dns?topic=dns-renew-an-existing-domain).
* Where do I find cost estimates for domain name registration?

You can estimate the cost of a service using the cost estimator on the provisioning pages for domain name registration. For example, log in to the [Domain Name Service](https://cloud.ibm.com/catalog/infrastructure/domain-registration) console and click Create in the Summary panel. In the Domains page, click the Register list menu. Pricing for registering domains is shown in a list menu in the Register New Domain section.
* How do I manage DNS zones?

Using the DNS interface, you can manage Forward Zones, Secondary Zones, and Reverse Records. To use this interface, select [Classic Infrastructure](https://%7BDomainName%7D/gen1/infrastructure/devices) from the menu in the IBM Cloud console, and then go to Network > DNS.
* How do I set up my reverse DNS?

Reverse DNS setup takes place using our [IBM Cloud console](https://%7BDomainName%7D/). For instructions on how to set up your reverse DNS, refer to [Managing reverse DNS records](https://cloud.ibm.com/docs/dns?topic=dns-add-or-edit-a-ptr-pointer-record).
* How long does it take for DNS changes to propagate?

DNS change propagation times depend on the time-to-live (TTL) setting for the DNS record. The default TTL is one day, which means any modifications to a domain name take one day to propagate throughout the entire internet. TTL can be lowered if you plan to make changes frequently; however, the lower the TTL is, the higher the load becomes on the name server.
<-- <section "id="section-update-authenticated-origin-pull-settings-option" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.----level: Specify the authenticated origin pull certificate or settings per zone or hostname level. Valid values: "zone", "hostname". The default is "zone".--hostname: The authenticated origin pull settings on a hostname. (hostname level only)----cert_id: The certificate id which the hostname is bundled to. (hostname level only)----enabled: Enable authenticated origin pull or not. Valid values: "on", "off".-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.<-- </section "id="section-update-authenticated-origin-pull-settings-option" "> --><-- <section "id="section-update-authenticated-origin-pull-setting-examples" "> --> Examples Update authenticated origin pull setting on zone level for domain 31984fea73a15b45779fa0df4ef62f9b. ibmcloud cis authenticated-origin-pull-settings-update 31984fea73a15b45779fa0df4ef62f9b --enabled on -i "cis-demo"
<-- </section "id="section-update-authenticated-origin-pull-setting-examples" "> --><-- </section "id="section-update-authenticated-origin-pull-setting" "> --><-- <section "id="section-show-authenticated-origin-pull-certificates" "> --> ibmcloud cis authenticated-origin-pull-certificates List zone level authenticated origin pull certificates for a domain.
Add-DnsServerResourceRecordA -Name "compute-0.ocp.dallas" -ZoneName "ibm.local" -AllowUpdateAny -IPv4Address "192.168.133.13" -CreatePtr -TimeToLive 00:00:10
Add-DnsServerResourceRecordA -Name "compute-1.ocp.dallas" -ZoneName "ibm.local" -AllowUpdateAny -IPv4Address "192.168.133.14" -CreatePtr -TimeToLive 00:00:10
Add-DnsServerResourceRecordA -Name "compute-2.ocp.dallas" -ZoneName "ibm.local" -AllowUpdateAny -IPv4Address "192.168.133.15" -CreatePtr -TimeToLive 00:00:10
Add-DnsServerResourceRecordA -Name ".apps.ocp.dallas" -ZoneName "ibm.local" -AllowUpdateAny -IPv4Address "10.208.242.131" -CreatePtr -TimeToLive 00:00:10
Add-DnsServerResourceRecordA -Name "api.ocp.dallas" -ZoneName "ibm.local" -AllowUpdateAny -IPv4Address "10.208.242.132" -CreatePtr -TimeToLive 00:00:10
Add-DnsServerResourceRecordA -Name "api-int.ocp.dallas" -ZoneName "ibm.local" -AllowUpdateAny -IPv4Address "10.208.242.132" -CreatePtr -TimeToLive 00:00:10

 Create DNS SRV record for etcd
Add-DnsServerResourceRecord -Srv -ZoneName "ibm.local" -Name "_etcd-server-ssl._tcp.ocp.dallas" -DomainName "etcd-0.ocp.dallas.ibm.local" -Priority 10 -Weight 0 -Port 2380
<-- <section "id="section-show-authenticated-origin-pull-certificate-option" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.CERT_ID: The ID of certificate. Required.----level: Specify the authenticated origin pull certificate or settings per zone or hostname level. Valid values: "zone", "hostname". The default is "zone".-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.<-- </section "id="section-show-authenticated-origin-pull-certificate-option" "> --><-- <section "id="section-show-authenticated-origin-pull-certificate-examples" "> --> Examples Get authenticated origin pull certificate 5a7805061c76ada191ed06f989cc3dac on zone level for domain 31984fea73a15b45779fa0df4ef62f9b . ibmcloud cis authenticated-origin-pull-certificate 31984fea73a15b45779fa0df4ef62f9b 5a7805061c76ada191ed06f989cc3dac -i "cis-demo"
<-- </section "id="section-show-authenticated-origin-pull-certificate-examples" "> --><-- </section "id="section-show-authenticated-origin-pull-certificate" "> --><-- <section "id="section-upload-authenticated-origin-pull-certificate" "> --> ibmcloud cis authenticated-origin-pull-certificate-upload Upload authenticated origin pull certificate for a domain.
ibmcloud cis firewall-create (-t, --type Type) (--json @JSON_FILE | JSON_STRING) [-d, --domain DNS_DOMAIN_ID] [-i, --instance INSTANCE] [--output FORMAT]
[Deprecated] ibmcloud cis firewall-create (-t, --type Type) (-s, --json-str JSON_STR | -j, --json-file JSON_FILE) [-d, --domain DNS_DOMAIN_ID] [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

-t, --type
: Type of firewall rule to create. Valid values: access-rules, ua-rules, lockdowns. Required.



* access-rules: Access Rules are a way to allow, challenge, or block requests to your website. You can apply access rules to one domain only or all domains in the same service instance.
* ua-rules: Perform access control when matching the exact UserAgent reported by the client. The access control mechanisms can be defined within a rule to help manage traffic from particular clients. This enables you to customize the access to your site.
* lockdowns: Lock access to URLs in this domain to only permitted addresses or address ranges.



-d, --domain
: DNS Domain ID. For ua-rules and lockdowns type rule, it is a required parameter.

--json
: The JSON file or JSON string used to describe a firewall rule. Required.



* For --type access-rules: The JSON data describing a firewall access rule as follows.



* Required fields are mode, configuration.



* mode: The type of action to perform. Valid values: block, challenge, whitelist, js_challenge.
* configuration: Target/Value pair to use for this rule.



* target: The request property to target. Valid values: ip, ip_range, asn, country.
* value: The value for the selected target.



* For ip the value is a valid ip address.
In Code Engine, [create a custom domain mapping](https://cloud.ibm.com/docs/codeengine?topic=codeengine-domain-mappings) for your app.
3. Set up an instance of [Cloud Internet Services (CIS)](https://cloud.ibm.com/catalog/services/internet-services) to manage your custom domain.
4. [Add the custom domain to the CIS instance](https://cloud.ibm.com/docs/cis?topic=cis-multi-domain-support).
5. [Configure a global load balancer](https://cloud.ibm.com/docs/cis?topic=cis-configure-glb) in CIS.
6. [Enable the HTTP proxy mode for the load balancer](https://cloud.ibm.com/docs/cis?topic=cis-proxy-modes) in CIS. This activates DDoS protection on Layer 7 and other CIS security features.
7. In Code Engine, turn off the public system provided domain mappings of your application. Go to your application, from the Domain mapping tab for your app, select No external system domain mapping.
8. Click Create to save the application revision.



For more information about DDoS in CIS, see [Dealing with Distributed Denial of Service attacks in CIS](https://cloud.ibm.com/docs/cis?topic=cis-distributed-denial-of-service-ddos-attack-concepts). For more ways to address Layer 7 attacks, see [Mitigating Layer 7 attacks in CIS](https://cloud.ibm.com/docs/cis?topic=cis-about-ibm-cloud-internet-services-ciscis-mitigate-layer7-attacks).
Configuring custom domain mappings for your app 

Domain mappings provide the URL route to your Code Engine applications within a project. With Code Engine, these mappings are automatically created, by default, whenever you deploy an application. However, you can map your own custom domain to a Code Engine application to route requests from your custom URL to your application from the Code Engine console or CLI.

If you want to target your application with a domain that you own, you can use a custom domain mapping. When you set a custom domain mapping in Code Engine, you define a 1-to-1 mapping between your fully qualified domain name (FQDN) and a Code Engine application in your project.

A custom domain mapping must point to only one application. However, you can configure multiple domain mappings to a single application.

You can create at most 80 custom domain mappings per project. See [Project quotas](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limitsproject_quotas).

When you create a custom domain mapping in Code Engine, the domain name that you use in the mapping must be unique in the region.

To create and set up custom domain mappings, complete these steps:



1. Review the [Considerations before you use custom domain mappings in Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-domain-mappingsconsiderations-custom-domain).
2. [Prepare to add a custom domain mapping](https://cloud.ibm.com/docs/codeengine?topic=codeengine-domain-mappingsprepare-custom-domain) (outside of Code Engine).
3. [Configure custom domain mappings](https://cloud.ibm.com/docs/codeengine?topic=codeengine-domain-mappingscustom-domain) (from the Code Engine console or CLI).
4.
After your apps are deployed, configure a custom domain mapping for them.



1. From the [Code Engine projects](https://cloud.ibm.com/codeengine/projects) page, click the name of one of the projects that you created.
2. Select Applications.
3. Select your global-app application.
4. Select Domain mappings.
5. Select Public for your visibility.
6. Click Create to create a custom domain mapping.
7. Click Select to choose an existing TLS secret and select global-tls.
8. Enter your fully qualified domain name; for example, www.example.com.
9. Note the CNAME target value. You need this value to set up routing for your domain in CIS.
10. Verify that the app name is global-app.
11. Click Create.
12. Repeat these steps to create a custom domain mapping for each application that you created.







 Step 6: Configure a health check 

When you created your applications, you set the Minimum number of instances to 1. Because there is always an instance of your app running in each region, you can set up a health check from your CIS instance to monitor the availability of pools. By setting up a health check, traffic is always routed to a running instance, making your app highly available.



1. From your CIS instance, navigate to Reliability > Global load balancers > Health checks.
2. Click Create.
3. Name your health check the same as your application name: global-app.
4. Set the Monitor type to HTTPS and the Port to 443.
5. Accept the defaults for the rest of the options. Note that if you are using an app other than codeengine/helloworld app, adjust any options that your app requires.
6. Click Create.



For more information, see [Setting up health checks](https://cloud.ibm.com/docs/cis?topic=cis-glb-features-healthchecks).
See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).

Added support for managing domain mappings with the CLI.
: Use the domainmapping command group to map your own custom domain to a Code Engine application to route requests from your custom URL to your application from the CLI. With this support, you can manage domain mapping with the CLI, in addition to the Code Engine console.



* See [Configuring custom domain mappings for your app](https://cloud.ibm.com/docs/codeengine?topic=codeengine-domain-mappings).
* See [Code Engine CLI reference (domainmapping command)](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-domainmapping).



Updated versions for buildpacks
: See [Choosing a build strategy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy).





 16 March 2023 

CLI version 1.42.0 released
: This CLI version updates support for secrets in the CLI such that you can define and work with various formats of secrets with the secret command group. See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).

Updated support for secrets in the CLI.
: Formats of secrets include basic authentication, generic, registry, SSH, and TLS. While you can continue to use the registry and repo command groups, take advantage of the unified secret command group.



* See [Working with secrets](https://cloud.ibm.com/docs/codeengine?topic=codeengine-secret).
* See [Code Engine CLI reference (secret command)](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-secret).







 10 March 2023 

Added troubleshooting information for why apps stop running
Add-DnsServerResourceRecordA -Name "etcd-0.ocp.dallas" -ZoneName "ibm.local" -AllowUpdateAny -IPv4Address "192.168.133.10" -TimeToLive 00:00:10
Add-DnsServerResourceRecordA -Name "control-plane-1.ocp.dallas" -ZoneName "ibm.local" -AllowUpdateAny -IPv4Address "192.168.133.11" -CreatePtr -TimeToLive 00:00:10
Add-DnsServerResourceRecordA -Name "etcd-1.ocp.dallas" -ZoneName "ibm.local" -AllowUpdateAny -IPv4Address "192.168.133.11" -TimeToLive 00:00:10
Add-DnsServerResourceRecordA -Name "control-plane-2.ocp.dallas" -ZoneName "ibm.local" -AllowUpdateAny -IPv4Address "192.168.133.12" -CreatePtr -TimeToLive 00:00:10
Add-DnsServerResourceRecordA -Name "etcd-2.ocp.dallas" -ZoneName "ibm.local" -AllowUpdateAny -IPv4Address "192.168.133.12" -TimeToLive 00:00:10
Add-DnsServerResourceRecordA -Name "compute-0.ocp.dallas" -ZoneName "ibm.local" -AllowUpdateAny -IPv4Address "192.168.133.13" -CreatePtr -TimeToLive 00:00:10
Add-DnsServerResourceRecordA -Name "compute-1.ocp.dallas" -ZoneName "ibm.local" -AllowUpdateAny -IPv4Address "192.168.133.14" -CreatePtr -TimeToLive 00:00:10
In addition, you are required to add a DNS provider following the steps in the [Connecting DNS providers](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-add-dns-provider&interface=uiadd-dns-provider-ui) topic. For this tutorial, you must add CIS as your DNS provider.

Initially HTTPS is configured from the user to Secrets Manager only.



1. Order a certificate in Secrets Manager



* Open the Secrets Manager service and select Secrets on the left.
* Click Add and then TLS certificates.
* Click on the Order a public certificate tile.
* Complete the form:



* Name - type a name you can remember.
* Description - enter a description of your choice.
* Under Certificate authority select your configured Let's Encrypt certificate authority engine.
* Under Key algorithm, pick your preferred algorithm,
* Bundle certificates - leave off
* Automatic certificate rotation - leave off
* Under DNS provider select your configured DNS provider instance
* Click on Select domains check the Select with wildcard and leave the domain itself unchecked and click on Done.



* Click Order.



2. Configure HTTPS from client web browsers to the CIS endpoint. In CIS configure TLS Security:



* Open the Security panel and choose TLS.
* For the Mode choose Client-to-edge. This will terminate HTTPS connections at the global load balancer and will switch to HTTP connections to the VPC load balancer.



3. In the CIS configure the global load balancer to use TLS:



* Open Reliability panel and choose Global Load Balancer.
* Locate the global load balancer created earlier and turn on Proxy.



4. In a browser open [https://lb.example.com](https://lb.example.com) to verify success.



Next configure HTTPS from CIS to the VPC load balancer.

Add an HTTPS listener to the VPC load balancers:



1. Navigate to VPC then Load balancers and click vpc-lb-region1.
2.
ibmcloud cis waf-setting DNS_DOMAIN_ID -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-show-waf-setting-options" "> --> 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.<-- </section "id="section-show-waf-setting-options" "> --><-- <section "id="section-show-waf-setting-examples" "> --> Examples Show WAF settings for domain 372e67954025e0ba6aaa6d586b9e0b60. ibmcloud cis waf-setting 31984fea73a15b45779fa0df4ef62f9b -i "cis-demo"
<-- </section "id="section-show-waf-setting-examples" "> --><-- </section "id="section-show-waf-setting" "> --><-- <section "id="section-update-waf-setting" "> --> ibmcloud cis waf-setting-update Update WAF setting. ibmcloud cis waf-setting-update DNS_DOMAIN_ID WAF_MODE -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-update-waf-setting-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.WAF_MODE: The mode of WAF setting. Valid values are: waf-enable , waf-disable. Required.-i, --instance: Instance name or ID.
You can create a custom domain mapping with your Code Engine application to your registered domain name with the Code Engine console.

In this scenario, let's create a custom domain mapping to an application with a TLS secret. For example, create a custom domain mapping to map the www.example.com domain to the myapp application.

Before you begin



* [Create a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-project).
* [Create an app](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-appdeploy-app-console).
* Obtain the signed TLS certificate and the private key.





1. From the [Code Engine Projects page](https://cloud.ibm.com/codeengine/projects), go to your project.
2. From the Overview page, click Domain mappings.
3. From the Domain mappings page, click Create to create your mapping.
4. From the Create a domain mapping page, specify the TLS secret to use with this domain mapping. Code Engine validates whether the certificate is signed by a trusted CA, and whether the certificate matches the provided custom domain name and private key.

To create a new TLS secret,



1. Click Create.
2. Add the TLS certificate, including all intermediate certificates, which are associated with your domain. If the certificate is provided to you as separate files, concatenate the content of the files. You can provide this information in a file.
3. Add the private key that corresponds to your certificate. You can provide this information in a file.



Example format for a certificate chain

-----BEGIN CERTIFICATE-----
...certificate...
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
...intermediate-certificate...
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
Getting started with Domain Name Registration 

Effective 30 June 2023, IBM Cloud will no longer support the Domain Name Registration service, which is offered in partnership with Tucows Inc. For more information, see [Domain Name Registration domain transfer](https://cloud.ibm.com/docs/dns?topic=dns-domain-name-registration-domain-transfer).

Domain name registration is the process of registering a user-friendly domain name, which identifies one or more IP addresses. IBM Cloud® Domain Name Registration offers customers a central location from which to view and manage their domains.

As an additional service, IBM Cloud offers secondary domain zones to our customers free of charge, allowing users to back up their primary domain records in the event of data loss or node failure.

IBM Cloud domain service functions similarly to any Domain Name System (DNS) management tool that you would use. You have the ability to interact with and edit existing domain records, add new records, and update information about reverse records. The primary benefit of using IBM Cloud over another DNS management service, or even managing it yourself, is that you have a central, reliable location in which all of your data is stored.



 Registering a new domain 



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 Services > Domain Registration to open the Domains page.
4. Choose the Register tab.

Select the Register Multiple Domains? option within the Register tab if you are registering multiple domains at one time.
5. Enter the new domain name in the Domain Name field.
6. Select the domain type from the Domain list.
7. Select the amount of time to reserve the domain from the Registration Time list.

The price for each time period is displayed next to the amount of time and will be charged to the account when the new domain is registered.
8.
For more information, see [Working with custom resolvers](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-custom-resolver).



* For IBM domains, you must also have an on-premises DNS resolver that points to either the user's DNS (Direct Link) or the custom resolver (Transit Gateway) in your VPC. You can then connect directly to the VPE and access IBM Cloud services.
* If accessing the VPC from another VPC, you only need a custom resolver, which forwards to the custom resolver in the VPC that has the VPE.



2. Create a VPE. For more information, see [Creating an endpoint gateway](https://cloud.ibm.com/docs/vpc?topic=vpc-ordering-endpoint-gateway).
3. Attach a new or existing security group (or modify the default security group) to allow inbound traffic to the VPE.



* Enable this feature within an account that has a VPC with a VPE already provisioned. To do so, you must [create a custom resolver](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-custom-resolver) before you can access the VPE over IBM Cloud Direct Link.

For IBM domains, you must have an on-premises DNS resolver that points to either the user's DNS (Direct Link) or the custom resolver (Transit Gateway) in your VPC. Then, you can connect directly to the VPE and access IBM Cloud services.

For resolutions of the VPE endpoints, you must forward the DNS requests to the custom resolvers within the DNS service that is provisioned within your VPC so that it can resolve the VPE addresses.



3. Verify that you have access from the direct link:

You should now be able to access a VPC API endpoint from an on-prem network through your Direct Link. You can use this VPC API endpoint over IBM Cloud Direct Link to provision additional resources in your VPC, such as VPEs for other IBM Cloud services.