vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [Setting up domains from other external providers](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domain-external)



* [Set up credentials for your provider](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domains-ext-cred)
* [Create a domain, or add an existing domain](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domains-ext-create)



* [Managing domains](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domains-manage)



* [Viewing domains in a cluster](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domains-manage-view)
* [Removing a domain from a cluster](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domains-manage-rm)
* [Updating a domain's IP addresses or hostname](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domains-manage-update)
* [Changing a cluster's default domain](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domain-manage-default)



* [Managing external provider credentials](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domains-manage-creds)



* [Viewing external provider credentials](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domain-manage-creds-view)
* [Removing external provider credentials](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domain-manage-creds-rm)
To use TLS termination, create a secret in the dl-reverse-proxy namespace that contains a TLS certificate for your custom domain. For example, if a TLS certificate is stored in IBM Cloud Certificate Manager that you want to use, you can import its associated secret into your cluster by running the following command. For more information, see [Custom domains with Ingress](https://cloud.ibm.com/docs/containers?topic=containers-managed-ingress-setupingress-custom-domain).

ibmcloud ks ingress secret create --name <secret_name> --cluster <cluster_name_or_ID> --cert-crn <certificate_crn> --namespace dl-reverse-proxy



5. Define an Ingress resource file that uses your custom domain to route incoming network traffic to an nginxsvc that you create in subsequent steps. Replace <custom_ingress_domain> with the domain that you registered, and <secret_name> with the secret that you created for your domain's TLS certificate.

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
name: dl-ingress-resource
annotations:
kubernetes.io/ingress.class: "private-iks-k8s-nginx"
nginx.ingress.kubernetes.io/proxy-read-timeout: "3600"
nginx.ingress.kubernetes.io/proxy-send-timeout: "3600"
spec:
tls:
- hosts:
- <custom_ingress_domain>
secretName: <secret_name>
rules:
- host: <custom_ingress_domain>
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: nginxsvc
port:
number: 80
Show more
6. Create the Ingress resource in your cluster.

kubectl apply -f dl-ingress-resource.yaml -n dl-reverse-proxy
* UI
* CLI
* API







 Editing a secondary zone 



 Editing a secondary zone using the UI 

To edit a secondary zone using the UI, take the following steps:



1. Navigate to the Custom resolver section of your DNS Services instance, and select the custom resolver in which you want to edit a secondary zone.
2. In the Custom resolver details page, select the Secondary zone tab.
3. Select the secondary zone you wish to edit.
4. Enter the changes for the secondary zone. Only the description and IP address fields can be edited.
5. Click Save.



To change the zone name, delete the secondary zone rule and create the rule again with the new name.





 Editing a secondary zone using the CLI 

To edit a secondary zone using the CLI, run the following command:

ibmcloud dns secondary-zone-update RESOLVER_ID SECONDARY_ZONE_ID [--transfer-from ADDRESS1,ADDRESS2] [--description DESCRIPTION] [--enabled true|false] [-i, --instance INSTANCE] [--output FORMAT]

Where:



* RESOLVER_ID is the ID of the custom resolver. Required.
* SECONDARY_ZONE_ID is the ID of the secondary zone. Required.
* --transfer-from value is the addresses of the DNS servers from where the secondary zone data is transferred.
* --description value is the description of the secondary zone.
* --enabled value is whether the secondary zone is enabled.
* -i, --instance value is the instance name or ID. If not set, the context instance specified by ibmcloud dns instance-target INSTANCE is used.
* --output value specifies output format. Currently, json is the only supported format.







 Editing a secondary zone using the API 

To edit a secondary zone using the API, follow these steps:



1. Set up your [API environment](https://cloud.ibm.com/apidocs/dns-svcsauthentication) with the correct variables.
2.
Create the custom domain mapping between the Code Engine myapp application and the custom domain, www.example.com. Use the TLS secret that you created in the previous step.

ibmcloud ce domainmapping create --domain-name www.example.com --target myapp --tls-secret mytlssecret

Example output

OK
Domain mapping successfully created.



The following table summarizes the options that are used with the domainmapping create command in this example. For more information about the command and its options, see the [ibmcloud ce domainmapping create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-domainmapping-create) command.



Table 1. Command description

 Option Description 

 --domain-name The name of the custom domain mapping. Specify the name of your custom domain, such as www.example.com. This value is required. 
 --target The name of the target Code Engine application. This value is required. 
 --tls-secret The TLS secret for the domain mapping. This value is required. 



Now you have a custom domain mapping that is created in Code Engine. However, requests that are sent to your application are not (yet) routed to your custom domain. Next, [complete the custom domain configuration with your domain registrar](https://cloud.ibm.com/docs/codeengine?topic=codeengine-domain-mappingscompleting-custom-domain-registrar).







 Completing the custom domain configuration with your domain registrar 

After the Code Engine custom domain mapping is created, a CNAME record that matches the fully qualified domain name must be added to the DNS settings of the custom domain. You can find the DNS settings in the configuration settings of the corresponding domain registrar. Complete this step so that traffic that targets your custom domain is routed to the Code Engine application as defined in your Code Engine custom domain mapping.



 How do I obtain the CNAME record for the custom domain mapping? 

Code Engine provides the CNAME target for your custom domain mapping.
Transferring an existing domain 

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).

After a domain has been registered, it can be transferred at any time. Transferring a domain from a third-party registrar to IBM Cloud® can streamline the domain management process. Transferring a domain does not affect the website, email, or DNS. It only changes the registrar that manages the domain records.

Follow these steps to transfer an existing domain to IBM Cloud.



 Transfer a single 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/86dadb3996e7fa2b119c2c09bda56dbc01297416/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 Transfer tab.
5. Enter the existing domain name in the Domain Name field.
6. Select the domain type from the Domain Type list.
7. Select the amount of time for which the domain will remain active from the Registration Time list.

The price for each time period is displayed next to the amount of time and is charged to the account when the new domain is transferred.
8. Click the Continue button to transfer the domain.







 Transfer multiple domains 

Domains can be transferred to IBM Cloud in bulk as well. Follow these steps to transfer multiple domains.



1. From your browser, open the [IBM Cloud® console](https://cloud.ibm.com/) and log in to your account.
2. Select the Menu icon !
ibmcloud cis ratelimit-analytics DNS_DOMAIN_ID --recent DURATION] --time-delta SECONDS] -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! ! ! !
<-- <section "id="section-ratelimit-analytics-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.--recent: The beginning of the requested time frame. Valid values are: 6h (6 hours ago), 12h, 1d (1 day ago), 1w (1 week ago), 1m (1 month ago), 2m, 3m. The default value is 1w.--time-delta: The time interval (seconds) of each analytic's record. Valid values: 60, 3600, 86400, 2592000. The default value is 3600.-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-ratelimit-analytics-options" "> --><-- <section "id="section-ratelimit-analytics-examples" "> --> Examples Get rate limit analytics for domain 31984fea73a15b45779fa0df4ef62f9b. ibmcloud cis ratelimit-analytics 31984fea73a15b45779fa0df4ef62f9b --recent 6h --time-delta 3600 -i "cis-demo" --output json
* Can I use a custom resolver that is already associated with a VPC?

Yes, the solution supports the use of a custom resolver that is already associated to a VPC. If a VPC already has a custom resolver, the automation makes uses of it and the DNS service and associates the new DNS domain that is created from the solution for hostname resolution.
* Can I associate a single VPC with multiple DNS zones that have the same name?

No, adding the same permitted network (for example, VPC) to two DNS zones of the same name is not allowed as mentioned [here](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-managing-permitted-networks&interface=uiadding-permitted-networks-ui). Therefore, when you select values for vpc_scale_storage_dns_domain and vpc_worker_dns_domain, ensure that they are unique and that there are no DNS zones that use either of those names that are already associated with the VPC that you might have specified in vpc_name.
* Where are the Terraform files that are used by the offering located?

The Terraform-based templates can be found in this public [GitHub repository](https://github.com/IBM-Cloud/hpc-cluster-symphony).
* What Spectrum Symphony and Spectrum Scale versions are used in cluster nodes deployed with this offering?

Cluster nodes that are deployed with this offering include IBM Spectrum Symphony 7.3.1 Advanced Edition. See the following for a summary of the features associated with each edition: [IBM Spectrum Symphony editions](https://www.ibm.com/docs/en/spectrum-symphony/7.3.1?topic=foundations-spectrum-symphony-editions).

If the cluster uses Spectrum Scale storage, the storage nodes include IBM Spectrum Scale 5.1.3.1 software. For more information, see the [IBM Spectrum Scale](https://www.ibm.com/docs/en/spectrum-scale/5.1.3) product documentation.
* What locations are available for deploying VPC resources?
* UI
* CLI
* API







 Managing permitted networks 

This section describes how to manage permitted networks for your IBM Cloud® DNS Services instance.



 Using the IBM Cloud console 



 Adding permitted networks 

DNS Services is a global service, therefore you may add permitted networks (for example, a VPC) from any IBM Cloud® region. This request adds the network to the DNS zone, thereby giving the network access to the zone. You can add up to 10 permitted networks to a DNS zone.

Newly created virtual server instances are automatically configured to use private DNS resolvers (161.26.0.7 and 161.26.0.8). Existing virtual server instances can take up to 3 minutes to be configured to use private DNS resolvers.



1. Select the desired zone from the table on the DNS Zones page.
2. Select the Permitted Networks tab.
3. Click the Add Network button.
4. In the panel that appears, select the region of your network from the Network Region list menu.
5. Select the desired network from the Network list menu that appears.
6. Click Add Network.



Adding the same VPC to two DNS zones of the same name is not allowed.





 Navigating from permitted networks to VPC overview 

You can navigate to the VPC overview page from the Permitted networks section by clicking on the VPC name. For example, in the following image, clicking on demo-vpc takes you to the overview page of the VPC named demo-vpc.

Zoom

![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

!
3. Add a redirect statement in the appropriate location within the configuration file. If needed, add your CDN domain as an additional ServerAlias to the virtual host for your origin.

Redirect /.well-known/acme-challenge/examplechallenge-fileobject http://dcv.akamai.com/.well-known/acme-challenge/examplechallenge-fileobject
4. Restart the Apache2 server with minimal downtime by using the following command:

apachectl -k graceful
5. Create an A record in your DNS between the CDN domain and the origin server's IP address.







 Nginx redirect configuration 

To configure an Nginx redirect, follow these steps:



1. Log in to the machine running the Nginx server.
2. Open your Nginx server configuration file. /etc/nginx/nginx.conf and /etc/nginx/conf.d/ are the default locations for the configuration files.
3. There are two equally valid methods for this step.



* Option 1: (recommended) Add a location block with a return directive to perform the redirect within the appropriate server block. If needed, add your CDN domain as an additional server_name to the server block for your origin.

server {
listen 80;
server_name origin.example.com cdn.example.com;

 Some server configuration directives
 ...

location = /.well-known/acme-challenge/examplechallenge-fileobject {
return 302 http://dcv.akamai.com$request_uri;
}

 Some more server configuration directives
 ...
}
* Option 2: Add a rewrite directive within the server block. If needed, add your CDN domain as an additional server_name to the server block for your origin.

server {
listen 80;
server_name origin.example.com cdn.example.com;

 Some server configuration directives
 ...
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://cloud.ibm.com/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://cloud.ibm.com/). 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. Higher loads have a potential to increase the response time to end users, which could impact their overall satisfaction.

The higher the TTL setting, the higher DNS performance is due to local ISP caching. The lower the TTL setting, the lower DNS performance is due to increased name resolution.

To verify TTL, check the Start of Authority (SOA) record for the domain. A great tool for reviewing domain information is offered by [CentralOps.net](http://centralops.net/co/)

TTL is listed in seconds. Divide by 60 to convert TTL to minutes, or by 3600 to convert to hours.





 After transferring a domain, how long does it take for the domain and the changes made to become visible? 

Your domain and/or changes to it are visible on IBM Cloud DNS servers immediately after the transfer completes.
Show details of an access application (Enterprise plan only).

ibmcloud cis access-app DNS_DOMAIN_ID ACCESS_APPLICATION_ID [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

ACCESS_APPLICATION_ID
: The ID of access application. 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 

Show details of access application a5836c2a7ea72d2e225890caea70ae32.

ibmcloud cis access-app 31984fea73a15b45779fa0df4ef62f9b a5836c2a7ea72d2e225890caea70ae32 -i cis-demo







 ibmcloud cis access-app-update 

Update an access application (Enterprise plan only).

ibmcloud cis access-app-update DNS_DOMAIN_ID ACCESS_APPLICATION_ID --name NAME --domain DOMAIN [--session-duration SESSION_DURATION] [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

ACCESS_APPLICATION_ID
: The ID of access application. Required.

--name value
: The name of the Application. Required.

--domain value
: The domain and path that Access will block. Required.

--session-duration value
: Defines the amount of time that the tokens issued for this application are valid. Valid values: 30m, 6h, 12h, 24h, 168h, 730h.

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

--output
ibmcloud cis firewall-rule-create 31984fea73a15b45779fa0df4ef62f9b --json '{"expression": "ip.src eq 93.184.216.1 and http.request.uri.path "^./wp-login.php$"", "action": "allow", "priority": 100, "paused": false, "description": "do not challenge login from office"}' -i "cis-demo"
<-- </section "id="section-create-a-firewall-rule-examples" "> --><-- </section "id="section-create-a-firewall-rule" "> --><-- <section "id="section-update-a-firewall-rule" "> --> ibmcloud cis firewall-rule-update Update a specific firewall-rule for a given DNS domain. ibmcloud cis firewall-rule-update DNS_DOMAIN_ID FIREWALL_RULE_ID --expression EXPRESSION] --action ACTION] --priority PRIORITY] --paused on|off] --description DESCRIPTION] -i, --instance INSTANCE] --output FORMAT]
ibmcloud cis firewall-rule-update DNS_DOMAIN_ID FIREWALL_RULE_ID (--json @JSON_FILE | JSON_STRING) -i, --instance INSTANCE] --output FORMAT]
Deprecated] ibmcloud cis firewall-rule-update DNS_DOMAIN_ID FIREWALL_RULE_ID (-s, --json-str JSON_STR | -j, --json-file JSON_FILE) -i, --instance INSTANCE] --output FORMAT] ! !!!!!! ! ! ! ! !
<-- <section "id="section-update-a-firewall-rule-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.FIREWALL_RULE_ID: The ID of firewall-rule.
--output OUTPUT
: Optional: Prints the command output in JSON format.

--domain-provider PROVIDER
: Required. The external DNS provider type. Specify --cis-ext.

--secret-namespace NAMESPACE
: Optional. The namespace that the domain TLS secret is created in. If no namespace is specified, the secret is created in the default namespace.

--domain-zone ZONE
: Optional. The Domain ID for your IBM Cloud Internet Services instance. This is a GUID value.







 Setting up domains from other external providers 

To add an Akamai or Cloudflare domain to your cluster, you must first apply credentials for the external provider to your cluster. Then, you can either add a domain that already exists in your external provider account, or you can create a new domain that registers with both your IBM Cloud and external provider accounts.



 Set up credentials for your provider 

To use a domain that is registered with Akamai or Cloudflare, you must add the external provider credentials to your cluster. Red Hat OpenShift on IBM Cloud uses these credentials to provision or access a domain from the external provider on your behalf. You can only add one set of credentials to your cluster.

Different providers might require different credentials, such as access tokens or secrets. Red Hat OpenShift on IBM Cloud does not provide the credentials; you must acquire them from the external provider.



 Add Akamai credentials 

Akamai

Run the command to add Akamai provider credentials to your cluster.

Note that registering credentials for Akamai requires the READ-WRITE permission for /config-dns endpoint in your external Akamai account.

ibmcloud oc ingress domain credential set akamai --cluster CLUSTER --access-token TOKEN --client-secret SECRET --client-token TOKEN --host HOST --zone AKAMAI_ZONE [-q]

This command is only required when creating an external domain with the Akamai provider.

-c, --cluster CLUSTER
: Required. The name or ID of the cluster where you want to add the credentials.

--access-token TOKEN
> * [ibm_cis_custom_pages](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/cis_custom_pages)<br> * [ibm_cis_dns_records](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/cis_dns_records)<br> * [ibm_cis_domain](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/cis_domain)<br> * [ibm_cis_edge_functions_actions](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/cis_edge_functions_actions)<br> * [ibm_cis_edge_functions_triggers](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/cis_edge_functions_triggers)<br> * [ibm_cis_filters](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/cis_filters)<br> * [ibm_cis_firewall](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/cis_firewall)<br> * [ibm_cis_firewall